Export Data


This page covers exporting query results to a file: where to open it, which formats are available, how to configure each SQL statement, and where to find the results after it runs.

What export does

Export writes SQL execution results to files: enter one or more statements and each result set is written to its own file. The export target is the query result, not the table structure; to include filters, put them in the SQL.

You can export multiple statements at once, separated by semicolons ;. Each statement is one item in the task list, where you can rename it and view its output location individually.

▶ Tutorial

Select format → enter SQL → run

Start an export

Export is not a persistent panel. It opens from the three entry points below, all with the same effect:

EntryLocationDescription
File → Export …File main menuGeneral entry, available once a connection is established
Export…Data area (DataGrid) context menuExport directly from a result set
Export Table…Context menu of a table node in the object treeFor a whole table

After opening, the window title shows the target connection, for example:

Export POSTGRES   pengtian@localhost   chinook.public

POSTGRES is the dialect; the rest is the connection name and the current database / schema. Query Sql in the window can be left empty for you to fill in, and it accepts multiple statements.

Options

export options

Full window view; the red box marks the export window

FieldDescription
Output PathOutput directory, default $home/steelsql-export; click the folder icon on the right to change it
File PatternFile name template, by default something like export_$tableName_20261027.csv; $tableName is replaced with the table name and the date part is generated for the current day
Query SqlSQL to execute; separate multiple statements with ;; comments start with -- and are not executed

File types

Four output formats; choose one:

TypeExtensionDescription
CSV file.csvPlain text, configurable delimiter and encoding, most universal
Excel file.xlsxGenerates a workbook directly, convenient for handing off to business users
JSON file.jsonOne object per line, suited to programmatic consumption
XML file.xmlStructured format for integrating with legacy systems

CSV options

When CSV is selected, four options are available:

OptionDefaultDescription
Put field names in first rowCheckedWrite column names in the first row
Value separatedComma(,)Field delimiter
Value wrapQuote if neededQuote when needed, so commas and newlines do not break the structure
Row separatedNewLine(\n)Row delimiter

Encoding & binary

Default Setting in the lower right applies to all formats:

OptionDefaultDescription
Encodeutf-8Output encoding
Escape Binary Data TohexBinary columns are written as hexadecimal
Auto detect binary text valuesCheckedAutomatically determine whether binary content is actually text

Task list

Click Next to go to the task list:

Export task list

Full window view; the red box marks the task list and output log

  • Each statement expands into a Task that you can open to inspect details.
  • FileName can be edited per task; you do not have to use the template-generated name.
  • Skip Columns skips specific columns: enter column names separated by the delimiter, case-insensitive.
  • Exp Res shows how many rows this statement actually exported.
  • Reveal File locates the generated file in the file manager.

The task list and the Output log at the bottom update together; you can see start / create file / done for each task.

Run

ButtonWhat it does
BackReturn to the options page to change settings
CancelCancel this export
ExportStart executing statements and writing files one by one

With Error continue checked, an error in one statement does not interrupt the remaining tasks; without it, execution stops at the first error.

When execution finishes, the files are in Output Path; their names come from File Pattern or from FileName in the task list.