Want to export data from SQL Server table to TXT file?
Try Withdata DBToFile, a SQL Server to TXT converter for Windows, Linux, and macOS, Export SQL Server data to TXT, 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.
- Support Windows, Linux, and macOS.
Export data from SQL Server table to TXT file
Connect to SQL Server -> Choose SQL Server table -> Set TXT file options -> Export SQL Server to TXT
Choose SQL Server and connect.

“Export From Table” for “SQL Server to TXT”.

Select TXT file type.

1. Choose SQL Server table.

2. Set TXT file options.
You can set “Delimiter” to:
- “,” : for exporting SQL Server to comma separated text file
- “TAB” : for exporting SQL Server to tab separated text file
- “|” : for exporting SQL Server to pipe separated text file
- “;” : for exporting SQL Server to exporting SQL Server toor semicolon separated text file
- “#” : for exporting SQL Server to hash tag separated text file
- “WHITESPACE” : for exporting SQL Server to whitespace delimited text file

3. Set rows options.

4. Export SQL Server data to TXT file.

After exporting, you can view output TXT files.

More about SQL Server to TXT converter
See Video: Export data from SQL Server table to TXT file in a few clicks
See also:
- Export SQL Server query results to TXT
- Export multiple similar SQL Server tables to one TXT file
- Batch export SQL Server tables to TXT files
SQL Server → TXT reference
Type mapping
| Value kind | in SQL Server | in TXT |
|---|---|---|
| Int | int | 1234, or right-aligned in a fixed-width column |
| Bigint | bigint | 9007199254740993 |
| Decimal | decimal(p,s) | 1234.56 |
| Float | float | 1.234e+10 |
| Text | nvarchar(n) | written as-is; padding depends on the chosen layout |
| Long text | nvarchar(max) | written as-is |
| Date | date | whatever the writer chose |
| Datetime | datetime2 | whatever the writer chose |
| Binary | varbinary(max) | not representable |
| Boolean | bit | Y / N, or 1 / 0, or TRUE / FALSE |
Dialect differences
SQL Server is a database server and TXT is a file format, so the gap is wider than a dialect difference – the rows below are where values and structure stop lining up.
| Property | in SQL Server | in TXT |
|---|---|---|
| port | 1433 | — |
| identifiers | [square brackets] | None by convention |
| row limit | SELECT TOP n | — |
| dates | datetime, datetime2, date, time | Whatever the writer produced; no convention is guaranteed |
| long text | nvarchar(max) | — |
| binary | varbinary(max) | Not supported |
| separator | — | Whatever was chosen - often fixed column widths |
| encoding | — | No declaration - UTF-8 works only with a BOM |
| typing | — | None - every field is text |
| shape | Tables of rows and columns | Free form; a parser has to be told the layout |
| ceiling | — | No formal limit |
Command line
| Side | Command |
|---|---|
| SQL Server | bcp |
| SQL Server (load) | bcp, or BULK INSERT |
Convert your data online, free
Free in-browser converters for CSV, Excel, JSON, XML and SQL: Withdata Online Data Conversion. Large files, batch conversion or scheduling? See the offline desktop apps, or browse all data conversion tools.
