Microsoft SQL Server
change data capture
TwinCommit captures changes from Microsoft SQL Server by reading its transaction log directly, then delivers each committed transaction exactly once to any supported target. Transaction-log capture without enabling SQL Server CDC jobs.
Microsoft SQL Server
SQL Server 2016–2025 · Azure SQL Managed Instance · Azure SQL Database (target)
- ✓FULL recovery model
- ✓Primary key on each replicated table
- ✓VIEW SERVER STATE and db_owner on the source database
Capture
How TwinCommit reads SQL Server
TwinCommit reads the active and backed-up transaction log directly, so you do not need SQL Server Agent CDC jobs or change tables.
SQL Server source docs →Apply
How TwinCommit writes to SQL Server
Set-based MERGE into BIN2-collated tables with an in-transaction checkpoint.
SQL Server target docs →Replicate SQL Server to…
SQL Server connector FAQ
Which SQL Server versions does TwinCommit support?
+
SQL Server 2016–2025 · Azure SQL Managed Instance · Azure SQL Database (target).
Does TwinCommit install anything in SQL Server?
+
No. TwinCommit reads the SQL Server log and creates no triggers, tables or procedures in the source database.
How does TwinCommit write to SQL Server?
+
Set-based MERGE into BIN2-collated tables with an in-transaction checkpoint.
Replicate your first table in five minutes.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.