Want to convert each table data in a SQL file to a separate TSV file at one time?
Try Data File Converter, a SQL converting tool for Windows, MacOS, and Linux, Convert tables in a SQL file to TSV files, Easy and Fast.
- Can run in GUI mode, Step by Step, just a few mouse clicks.
- Can run in Command line, for Scheduled Tasks and Streams.
- Convert files locally and privately, avoid uploading large SQL file(s) to online services.
Download Withdata DataFileConverter
Windows 64 bit
Windows 32 bit
Linux .deb (For Debian, Ubuntu) 64 bit
Linux .rpm (For Red Hat, Fedora, SUSE) 64 bit
MacOS 64 bit
Convert each table data in a SQL file to a separate TSV file
Select source SQL file -> Set target TSV file -> Convert SQL table to TSV
Click “Start a New Convert” at task dialog.
then show the wizard.
Select From “File” “SQL” To “Files” “TSV”.
1. Open a source SQL file, select tables to convert to TSV files.
2. Config target TSV files.
3. Summary.
List selected tables.
4. Convert each SQL table to a separate TSV file.
After converting, you can view output TSV files.
Convert each SQL table to a separate TSV file in command line
Save “SQL table to TSV” session, then you can:
- Convert each SQL table to a separate TSV file in Windows command line.
- Convert each SQL table to a separate TSV file in Linux command line.
- Convert each SQL table to a separate TSV file in macOS command line.
Set scheduled tasks for converting each SQL table to a separate TSV file
You can schedule and automate this SQL table to TSV converting task by:
- Save session and create .bat (Windows) or .sh (Linux/macOS) file for “SQL table to TSV” conversion.
- Set scheduled task for “SQL table to TSV” conversion.
FAQ
More about Withdata DataFileConverter – Tables in SQL file to TSV converter
Download Withdata DataFileConverter
Windows 64 bit
Windows 32 bit
Linux .deb (For Debian, Ubuntu) 64 bit
Linux .rpm (For Red Hat, Fedora, SUSE) 64 bit
MacOS 64 bit
See Video: Convert each table data in a SQL file to a separate TSV file at one time
SQL → TSV reference
Type mapping
| Value kind | in SQL | in TSV |
|---|---|---|
| Int | INT | 1234 |
| Bigint | BIGINT | 9007199254740993 |
| Decimal | DECIMAL(p,s) | 1234.56 |
| Float | DOUBLE PRECISION | 1.234e+10 |
| Text | VARCHAR(n) | unquoted; a tab in the value splits the column |
| Long text | TEXT / CLOB | unquoted; newlines break the row |
| Date | DATE | 2026-09-18 |
| Datetime | TIMESTAMP | 2026-09-18 14:30:00 |
| Binary | BLOB / BYTEA | not representable |
| Boolean | BOOLEAN / SMALLINT | TRUE / FALSE |
| JSON | JSON / TEXT | the whole JSON value as-is (its own quotes stay) |
Dialect differences
Both SQL and TSV are file formats, so what differs below is how each one chooses to represent a value.
| Property | in SQL | in TSV |
|---|---|---|
| identifiers | Two competing conventions: single-quoted literals and diale... | Rarely used, which is exactly why tabs in data break it |
| dates | Depends on the dialect: DATE literals, TO_DATE(), or plain ... | Conventional text: 2026-09-18 or 2026-09-18 14:30:00 |
| binary | Dialect-specific: X-quoted literal, 0x hex, or decode() | Not supported - must be encoded |
| separator | Statement terminators (;) | Tab |
| encoding | No declaration | No declaration - UTF-8 works only with a BOM |
| typing | Types belong to the target database, and they differ betwee... | None - every field is text |
| shape | Statements; a dump usually means CREATE TABLE plus INSERT rows | Flat table, optional header row |
| ceiling | No formal limit, but a single INSERT statement has to fit i... | No formal limit |
Data File Converter without the manual work
For batch jobs, large files and scheduling use the Data File Converter converter — an offline desktop app for Windows, Linux and macOS. Free trial.
New to the format? Read what a TSV file is (and how it differs from CSV).