CDC source
Capture committed SQL Server changes
Validate the available capture mode, privileges, logging settings, retention, and restart position before promising a continuous stream.
Compare source modes →
CDC source and relational destination
SQL Server with SQL Flow
This page describes SQL Server's continuous-data role in SQL Flow. It is separate from Omni Loader's one-time bulk-migration support and focuses on capture, delivery, and recovery behavior.
Supported direction
Where SQL Server fits in the continuous path
CDC destination
Keep SQL Server current
Confirm stable keys, compatible types, schema ownership, apply concurrency, retry policy, and the lag target that operations will measure.
Review destination behavior →Deployment checks
Test the contract around the real SQL Server environment
Access
Can SQL Flow reach the SQL Server interfaces and metadata required for its supported direction?
Record meaning
Do keys, before-images, large values, schema changes, and transaction boundaries match the downstream contract?
Recovery
Can checkpoints, retained history, retries, and target state survive the outage scenarios you expect?
Validate the SQL Server CDC path before production.
Bring the engine version, hosting model, permissions, keys, workload, and recovery goals. We will identify the checks that matter for this direction.
SQL Flow handles automatically
The software does the migration work.
- SQL Flow selects provider-aware capture, type handling, and apply behavior.
- Supported capabilities and prerequisites are matched to the chosen database.
- Database-specific differences are applied without rebuilding the migration.
You choose
Keep control of the decisions that matter.
- Choose the source and target database.
- Select among the available CDC modes.
- Choose type mappings and target-apply policy.