Move SQL Server data slices with a portable SQLite container
Extract specific rows from a SQL Server table into a single SQLite file, edit them offline, and push changes back to SQL Server in scripted runs. SqlDataPack, created by zachtbeer, is a Windows .NET utility for developers and DBAs who need repeatable, portable data transfers. It offers a CLI for automation, a NuGet library for integration, and WinGet support for installation, making it suitable for seeding test databases and sharing small datasets among team members.
What the tool actually moves and how it does it
SqlDataPack exports table slices into a single SQLite container so you get a portable file that holds only the rows and columns you select. The tool uses SQLite as an intermediary, which lets you open and edit the exported data in any SQLite-compatible editor, then import the same file back into a SQL Server instance. The developer provides both a CLI and a NuGet package for programmatic use.
How it behaves during scripted operations and CI/CD
The CLI supports scripted and automated workflows, letting you call export and import commands from build servers or scheduled jobs. Because it operates as a command-line .NET tool, you can install it globally with the .NET SDK and invoke it from batch files or pipelines. WinGet availability simplifies deployment on Windows build agents where package management is required.
Safety, permissions, and offline editing model
SqlDataPack separates transport from live changes by writing a SQLite file for offline edits, which reduces direct write operations on production servers during modification. That design implies you edit data outside the server and reapply changes in a controlled import step. The app requires access to SQL Server for exports and imports and runs under the permissions of the invoking process, so account rights determine what it can read or write.
Practical recommendation for developers and QA teams
SqlDataPack suits developers, QA engineers, and DevOps staff who need repeatable, scriptable transfers of selected SQL Server data without moving entire schemas. Expect an offline edit workflow that confines changes to a portable file before any server writes occur, and plan permissions accordingly. Recommended.
