MS SQL Server Change Tracking Agent for Gluesync: Key Features
Core principles
This agent establishes a connection to MS SQL Server via a built-in JDBC driver.
Change data capture
This agent implements the so-called Change Tracking feature to catch field-level changes in rows in tables that have Primary Key constraints on MS SQL Server 2008 and above.
If you don’t have Primary Keys on tables or you’re looking for the Change Data Capture (CDC) feature based on MS SQL Server’s SQL Agent, plase check out our Gluesync CDC agent for MS SQL Server’s Transaction Logs | Change Data Capture.
Platform supported features
| Feature | Support | Notes |
|---|---|---|
Target role |
✅ |
Streams data into SQL Server instances (on-prem or SQL Azure) through the bundled JDBC driver with TLS/pooling. |
Source role |
✅ |
Uses SQL Server Change Tracking metadata tables to read row-level deltas when primary keys are present. |
Snapshots |
✅ |
Entities can run full snapshots ahead of Change Tracking to seed targets. |
CDC |
✅ |
Continuously queries Change Tracking functions for incremental changes. |
CDC type |
Change Tracking |
Relies on SQL Server’s Change Tracking feature (requires PKs on tracked tables). |
Bulk load |
✅ |
Can participate in staging-table Bulk load flows (SqlBulkCopy) when targeting SQL Server. |
Source persisted internal cache |
N/A |
State is maintained by SQL Server Change Tracking tables plus Core Hub metadata. |
Target persisted internal cache |
N/A |
Writes go straight to SQL Server without extra buffering. |
Driver / connector |
Built-in JDBC driver |
Gluesync bundles the official SQL Server JDBC driver. |
Chains |
✅ |
Supported. |
Truncate operation support (reading) |
N/A |
Source agent can capture and forward TRUNCATE operations to the target but MS SQL Server denies TRUNCATE operations on tables with CDC enabled. |
Truncate operation support (writing) |
✅ |
Target agent honors the “TRUNCATE before snapshot” option when enabled. |