{"slug":"databases-sql-studio","title":"SQL Studio","description":"Browse, edit, and manage your PostgreSQL data directly from the DanubeData dashboard — no client to install, no credentials to copy.","section":"Features","url":"https://docs.danubedata.ro/databases-sql-studio","markdown_url":"https://docs.danubedata.ro/databases-sql-studio.md","breadcrumbs":[{"title":"Features","slug":null},{"title":"Databases","slug":"databases-overview"},{"title":"SQL Studio","slug":"databases-sql-studio"}],"headings":[{"level":1,"title":"SQL Studio","id":"sql-studio"},{"level":2,"title":"Overview","id":"overview"},{"level":2,"title":"Availability","id":"availability"},{"level":2,"title":"Opening SQL Studio","id":"opening-sql-studio"},{"level":2,"title":"Browsing Data","id":"browsing-data"},{"level":2,"title":"Editing Data","id":"editing-data"},{"level":2,"title":"Table Operations","id":"table-operations"},{"level":2,"title":"SQL Editor","id":"sql-editor"},{"level":2,"title":"Schema Tools","id":"schema-tools"},{"level":2,"title":"Importing Data","id":"importing-data"},{"level":2,"title":"Safety & Auditing","id":"safety-auditing"},{"level":2,"title":"Next Steps","id":"next-steps"}],"format":"markdown","word_count":805,"content":"# SQL Studio\n\nBrowse, edit, and manage your PostgreSQL data directly from the DanubeData dashboard — no client to install, no credentials to copy.\n\n## Overview\n\nSQL Studio is an in-browser data studio included free with every managed PostgreSQL database:\n\n- **Table editor** - Edit rows with staged, transactional commits\n- **SQL editor** - Ad-hoc queries with a read-only safe mode\n- **Schema tools** - Create-table builder, table operations, ER diagram\n- **Objects browser** - Functions, triggers, views, roles, extensions, RLS policies\n- **Zero install** - Runs entirely in your dashboard\n\nQueries are executed by an isolated agent that runs inside your own tenant environment. Your database credentials never leave the platform.\n\n## Availability\n\n- SQL Studio works with **managed PostgreSQL instances only**. It is not available for MySQL or MariaDB.\n- It is not available on demo accounts.\n- There is no additional cost — Studio is included with every managed PostgreSQL plan.\n\n## Opening SQL Studio\n\n1. Go to **Databases** in the dashboard\n2. Select your PostgreSQL instance\n3. Open **SQL Studio**\n\nIf your instance hosts multiple databases, use the database selector in the top bar to switch between them.\n\n## Browsing Data\n\n- The sidebar lists all schemas and tables; type in the filter box to find a table quickly\n- Click a table to open its rows in the data grid\n- Click a column header to sort; click again to flip the direction\n- Add per-column filters (`=`, `!=`, `<`, `>`, `LIKE`, `ILIKE`, `IS NULL`, …) with **+ Filter**\n- Use the pager in the footer to move through large tables\n\n## Editing Data\n\nEditing is off by default. Flip the **Write mode** toggle in the top bar to enable it.\n\nChanges are **staged locally** before anything touches the database:\n\n- **Double-click a cell** to edit it. Use the **NULL** / **DEF** buttons to set the cell to `NULL` or the column default explicitly\n- **+ Add row** appends a new row inline; columns you leave untouched use their database defaults\n- The **delete** toggle marks a row for deletion (shown struck-through until you commit)\n- Pending changes are highlighted, and the toolbar shows the count\n\nClick **Commit** to apply everything in a **single database transaction** — if any change fails, nothing is written. Click **Discard** to drop all pending changes. A single commit can carry up to 500 staged changes.\n\nNotes:\n\n- Tables without a primary key are read-only in the grid (use the SQL editor instead)\n- An **Insert (form)** drawer and a CSV import are also available for adding rows\n- If you navigate away with pending changes, Studio asks whether to commit or discard them\n\n## Table Operations\n\nRight-click a table in the sidebar (Write mode required for anything that modifies the database):\n\n- **Open** - View the table\n- **Truncate** - Delete all rows (asks for confirmation)\n- **Drop** - Delete the table; you must type the table's name to confirm\n- **Rename** - Change the table name\n- **Duplicate** - Copy the table structure, optionally with its data\n- **Copy name** / **Copy CREATE statement** - Copy to clipboard (the CREATE statement is reconstructed from the catalog and is approximate)\n\nRight-click an empty area of the sidebar for **New table** — a visual builder where you define columns, types, nullability, defaults, and the primary key.\n\n## SQL Editor\n\nThe **SQL** tab runs ad-hoc statements:\n\n- Queries run in a **read-only safe mode** by default — writes are rejected until you enable Write mode\n- With Write mode on, destructive statements (for example `DROP` or `TRUNCATE`) ask for confirmation before running\n- The editor executes **one statement per run**; for bulk data changes, use the table editor's staged commits or the CSV import\n- Save frequently used queries as **snippets**, and re-open anything from your **history** with one click\n- Export query results as **CSV** or **JSON**\n\n## Schema Tools\n\n- **Structure** tab - Columns, constraints, indexes, and foreign keys for the selected table\n- **Diagram** tab - A live ER diagram of the schema: tables, columns, and foreign-key relationships, with pan and zoom\n- **Database** tab - Browse functions, triggers, views, roles, extensions, and row-level-security policies, including their definitions\n\n## Importing Data\n\nUse **Import CSV** in the table footer (Write mode required) to bulk-load rows from a CSV file. The wizard lets you map CSV columns to table columns before inserting.\n\n## Safety & Auditing\n\n- Studio opens **read-only**; every write requires the explicit Write-mode toggle\n- Row changes apply as one atomic transaction you can review and discard before committing\n- Dropping a table requires typing its name\n- **Every write is recorded** in your instance's query log (who, what, when, and the SQL that ran)\n- Queries run through a per-tenant isolated agent — no shared query infrastructure between customers\n\n## Next Steps\n\n- [PostgreSQL Guide](https://docs.danubedata.ro/databases-postgresql)\n- [Database Backups](https://docs.danubedata.ro/databases-backups)\n- [Database Replicas](https://docs.danubedata.ro/databases-replicas)\n\nNeed help? Contact support through the dashboard.\n","prev":{"title":"PostgreSQL","slug":"databases-postgresql","url":"https://docs.danubedata.ro/databases-postgresql","markdown_url":"https://docs.danubedata.ro/databases-postgresql.md","json_url":"https://docs.danubedata.ro/databases-postgresql.json"},"next":{"title":"MariaDB","slug":"databases-mariadb","url":"https://docs.danubedata.ro/databases-mariadb","markdown_url":"https://docs.danubedata.ro/databases-mariadb.md","json_url":"https://docs.danubedata.ro/databases-mariadb.json"},"index_url":"https://docs.danubedata.ro/index.json"}