Moving data
Import and export
Load CSV, Excel and JSON files into your tables, export results and whole tables, and run big SQL scripts with a live log.
Import a file
Right-click a database, a schema or a table → “Import file…”. It takes CSV or text, Excel (xlsx, xls, ods) and JSON.
- File: pick it and check the preview of its first rows. Qrulla detects the format; adjust if needed:
- CSV: separator (automatic, comma, semicolon, tab), whether the first row has the names, and the encoding (UTF-8 or Windows, the one Spanish Excel uses).
- Excel: the sheet.
- Numbers with a decimal comma (1.234,56), the date order (day/month/year, month/day/year, year/month/day) and the text that means empty.
- Target: a new table (with its name) or an existing one, where you add the rows or replace them.
- Columns: match each file column to a table column, pick its type and which is the key, or mark it not to import.
- If a row does not fit: stop and import nothing, or skip it and note it.
Everything is imported in a transaction: if it fails or you cancel, nothing is left half done. At the end you see how many rows went in and, if you skipped any, which and why.
If the file is a .sql script, it isn't imported as data: use “Run SQL file…”.
Export a result or a table
“Export” in the grid or in an editor result saves what you see as:
| Format | Details |
|---|---|
| CSV | Comma, semicolon (for Spanish Excel) or tab separator; optional headers; “Excel friendly” so accents show. |
| JSON | A list of objects. Numbers stay numbers, without losing decimals. |
| Excel | Numbers and dates as Excel values. Past a million rows it goes on in another sheet. |
| SQL | An INSERT per group of rows, optionally with the CREATE TABLE, indexes and keys. |
The export runs in the background and can be cancelled; if you cancel it, no half-written file is left.
Export several tables
Right-click a database or a schema → “Export tables…”. Pick the tables, the format and a folder: one file per table is created. An existing file isn't replaced; the new one is called “table (2)”.
Run an SQL file
Right-click a database, a schema or a table → “Run SQL file…”. It's for dumps from mysqldump, pg_dump or other programs, or any script, however big.
- Encoding: UTF-8 (the usual today) or Windows-1252 if accents come out wrong.
- If a statement fails: stop there or go on with the next one.
Each statement runs exactly as written, in order and on one connection. While it runs, the log says what's being created, how many rows go into each table and on which line something failed. What already ran isn't undone when you cancel.
The script of some objects
To save the SQL that creates tables, views and the rest, with or without data, use “Export SQL…” in the tree. See Databases, schemas and objects.
Something missing or unclear? Write to support@qrulla.com.