Import and export SQL Server data

Move SQL Server data with visible scope, formats, NULL handling and destination review.

Tablyne keeps SQL Server import and export centered on visible scope, format choices and destination review.

Choose the data movement scope

Tablyne defines:

  1. Whether the source is a table, filtered rows or a query result.
  2. Which formats are supported.
  3. Whether identity, computed and generated columns are included.
  4. How NULLs, binary values, dates and collations are represented.
  5. Whether the operation is previewed before writing.
  6. How a failed batch is rolled back.

These choices keep SQL Server data movement distinct from PostgreSQL’s pg_dump terminology and SQLite’s file-export limitations.

Review the destination

An import that writes rows shows the target relation, mapped columns and operation before execution. A SQL Server grid edit also carries the captured rowversion when an import updates existing rows. If a row changed between the preview and commit, the batch must stop instead of replacing the newer value.

An export states whether it contains displayed rows, filtered rows or the full relation. A query-result export uses the result that was already executed rather than silently running the query again.

Review the destination

Review the destination, mapped columns and rowversion condition before committing an import that updates existing rows.