> ## Documentation Index > Fetch the complete documentation index at: https://archie.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # SQL Playground > Run SQL against your app's database. The SQL Playground is a direct query interface to your project's database. It runs in the same connection your app uses, so what you can do depends on the role you are signed in as. To access this tool, select **SQL Playground** from the left-hand sidebar menu. SQL Playground overview ## Query Editor The main "Playground" area allows you to write standard SQL statements. You can perform simple `SELECT` queries or complex `JOIN` operations (e.g., linking `students` with `cities`). ### Execution Methods There are multiple ways to execute your code, giving you flexibility depending on your workflow: 1. **Line Execution:** Click the **Blue Play Triangle (▶)** located in the gutter next to a specific line number to run just that statement. 2. **Context Menu (Right-Click):** Right-click anywhere in the editor to open a menu where you can select **Execute SQL Query**. 3. **Keyboard Shortcut:** Press **`Ctrl + Enter`** to execute the query immediately without using the mouse. SQL Playground execution methods: line execution, right-click, Ctrl+Enter 4. **Operations Panel:** Click the large **Run (▶)** button located in the top-right corner. A "Select Operation" panel lists suggested or context-aware queries (e.g., "Select All From students"). SQL Playground Operations panel with Run button and suggested queries ### Toolbar Actions The toolbar at the top of the editor provides tools to manage your code: SQL Playground toolbar with Format, History, Download, Copy, Clear actions * **Format SQL:** Use the **Magic Wand** icon to automatically format and indent your SQL code for better readability. * **Query History:** Access a log of your previously executed queries. * **Download SQL:** Download the current queries to your local machine. * **Copy SQL:** Use the **Copy** icon to copy the editor's content to your clipboard. * **Clear Editor:** Use the **Broom** icon to clear or delete all queries from the editor. ## Results Panel The **Results** section at the bottom displays the output of your execution. * **Data Grid:** The data is presented in a table format with columns corresponding to your query (e.g., `first_name`, `age`, `name_city`). * **Row Count:** The total number of records returned is displayed in the top right (e.g., "9 rows found"). * **Column Visibility:** You can customize the view by clicking the column selector icon in the results header to toggle specific columns on or off. SQL Playground Results panel with data grid and column visibility ## DDL statements Schema changes (CREATE, ALTER, DROP) are not executed in the playground — they belong in the [data model](/features/backend/data-model/overview) workflow which produces tracked migrations. {/* VERIFY: confirm whether DDL is rejected or allowed with a warning */} ## Per-environment data The playground binds to the active environment. Switch environments to query staging or production data. Production access is typically restricted to admin roles. ## Best practices * **Use transactions** for multi-statement writes — `BEGIN; ...; COMMIT;` * **Limit destructive queries** — always test with a `WHERE` clause first * **Use `EXPLAIN`** to inspect query plans for slow reads * **Avoid manually inserting** rows that should go through the application layer (validation, hooks) ## FAQ Yes. Audit logs include the actor, query, and runtime. Use a custom function with a scheduled trigger and put the SQL there.