Want to export data from SQL Server table to JSON lines (JSONL / NDJSON / LDJSON)?
Try Withdata DBToFile, Support Windows, Linux, and macOS, Export SQL Server data to JSON lines (JSONL / NDJSON / LDJSON), 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.
Download Withdata DBToFile
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
JSON Lines text format (JSONL), also called Newline-delimited JSON (NDJSON), or Line-delimited JSON (LDJSON). JSON Lines files may be saved with the file extension .jsonl, *.ndjson, *.ldjson.
Export data from SQL Server table to JSON lines (JSONL / NDJSON / LDJSON)
Login to SQL Server -> Choose SQL Server table -> Set JSON lines file options -> Export SQL Server to JSON lines (JSONL / NDJSON / LDJSON)
Choose SQL Server and logon.
“Export From Table” for “SQL Server to JSON lines (JSONL / NDJSON / LDJSON)”.
Select JSON file type.
1. Choose SQL Server table.
2. Set JSON lines (JSONL / NDJSON / LDJSON) file options.
3. Set rows options.
4. Export SQL Server data to JSON lines (JSONL / NDJSON / LDJSON) table.
After exporting, you can view output JSON lines (JSONL / NDJSON / LDJSON) file.
More tools for JSONL / NDJSON / LDJSON.
Download Withdata DBToFile
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
SQL Server → JSON Lines reference
Type mapping
| Value kind | in SQL Server | in JSON Lines |
|---|---|---|
| Int | int | 1234 (number) |
| Bigint | bigint | 9007199254740993 |
| Decimal | decimal(p,s) | 1234.56 (number) |
| Float | float | 1.234e10 (number) |
| Text | nvarchar(n) | "text" (string) |
| Long text | nvarchar(max) | "multi-line\ntext" |
| Date | date | "2026-09-18" (string) |
| Datetime | datetime2 | "2026-09-18T14:30:00Z" (string) |
| Binary | varbinary(max) | "base64:..." (string) |
| Boolean | bit | true / false (boolean) |
| JSON | nvarchar(max) | nested object on the same line |
Dialect differences
SQL Server is a database server and JSON Lines 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 JSON Lines |
|---|---|---|
| port | 1433 | — |
| identifiers | [square brackets] | Double quotes; backslash escapes (a newline inside a string... |
| row limit | SELECT TOP n | — |
| dates | datetime, datetime2, date, time | No date type: dates arrive as strings |
| long text | nvarchar(max) | — |
| binary | varbinary(max) | Not supported natively - base64 inside a string |
| separator | — | Newline between records |
| encoding | — | UTF-8 by definition |
| typing | — | Same as JSON, but records cannot nest across lines |
| shape | Tables of rows and columns | Flat stream |
| ceiling | — | Streams, so it scales past what a single JSON document can ... |
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.