MS SQL Server 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 Change Data Capture (CDC), a set of APIs that put their foundations directly top of the SQL Server transaction logs making possible to get incremental changes from database version 2008 via the SQL Agent jobs, this CDC is compatible with Enterprise edition and Standard from 2022 onwards. This agent can work even if your tables do not have Primary Keys physically defined on tables, unlike the Change Tracking feature.
Platform supported features
| Feature | Support | Notes |
|---|---|---|
Target role |
✅ |
Streams data into SQL Server through the bundled JDBC driver with TLS, pooling, and SQL Azure support. |
Source role |
✅ |
Captures transaction-log changes via SQL Server CDC jobs managed by SQL Agent (Enterprise + Standard 2022+). |
Snapshots |
✅ |
Entities can run Core Hub snapshots to seed SQL Server tables before CDC takes over. |
CDC |
✅ |
Continuously replays log blocks surfaced by SQL Server’s Change Data Capture APIs. |
CDC type |
Transaction logs (SQL Agent CDC) |
Reads redo/undo information from the transaction log via CDC jobs. |
Bulk load |
✅ |
Supports staging-table Bulk load flows using SqlBulkCopy for high-volume mirroring. |
Source persisted internal cache |
N/A |
Relies on Core Hub metadata tables; no disk-backed cache on the agent. |
Target persisted internal cache |
N/A |
Writes land directly on SQL Server without extra buffering. |
Driver / connector |
Built-in JDBC driver |
Gluesync ships the vendor JDBC driver for secure connectivity. |
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 in Core Hub. |