What Is Table Synchronisation?
Table synchronisation keeps selected rows aligned between SQL Server databases or environments using an initial copy and ongoing change capture.
Table synchronisation moves or reconciles table data so a source and target remain aligned. Teams use it for migrations, reporting copies, and data movement between SQL Server environments.
Definition
A synchronisation process usually makes an initial copy, then identifies inserts, updates, and sometimes deletes that happened afterward. It needs a way to track progress, such as a watermark, change tracking, or another change feed.
What needs deciding
- Which tables and rows are in scope, and which system is authoritative.
- How changes are detected and how often they are applied.
- How deletes, conflicting writes, and schema changes are handled.
- How lag, failed batches, row counts, and data correctness are verified.
Operational example
During a migration, a team copies a large orders table to the new database. Later batches copy only rows changed since the last checkpoint. Before cutover, the team checks the remaining lag and reconciles counts and representative records.
Common pitfalls
Matching row counts does not prove that row values agree. A timestamp watermark can also miss changes if it is not updated consistently or if time boundaries are handled incorrectly. Plan a reconciliation step.
SQL Cockpit context
SQL Cockpit supports table synchronisation workflows and helps teams review progress and validation evidence as they prepare a migration or ongoing data movement.
FAQ
Is table synchronisation the same as a backup?
No. A backup preserves a recoverable database state; synchronisation keeps selected data aligned between systems.
Does synchronisation automatically handle schema changes?
No. Schema compatibility needs its own checks and change process.