Exporting data
You can export a whole table or the result of a query. Both use the same dialog.
- A table — right-click it, or use Table → Export as CSV/JSON with the table tab open.
- A query result — Export Results in the SQL editor. Because results are cached, the export does not re-run the query.
Formats
| Format | Notes |
|---|---|
| CSV | Delimiter defaults to a comma |
| TXT | Delimiter defaults to a tab |
| JSON | Array of objects |
| XLSX | Excel workbook |
| ODS | OpenDocument spreadsheet |
| XML | One element per row |
| SQL | INSERT statements — structure only, or structure and data |
Pick the format, set the file path, click Export. The dialog reports where the file was saved.
SQL exports
The SQL format has one extra choice: DDL only or DDL + data. DDL only gives you the CREATE TABLE statement, which is what you want when moving structure to another environment.
For a whole database, the sidebar has a faster path: right-click the database → Dump SQL file ▸ Structure and data or Structure only. The same submenu exists on a single table.
Dumping vs backing up
Three things overlap here, so:
- Export — one table or one result set, in any of the formats above. For handing data to a person or another system.
- Dump SQL file — a
.sqlfile withCREATE/INSERTstatements for a table or a whole database, straight from the sidebar. - Backup and restore — a full database dump with a progress bar, plus the restore side with error handling. For actual backups.
Moving data to another server
If the destination is another database rather than a file, do not export and re-import — Data transfer copies tables, views and routines directly between connections, including across different engines.
