MS SQL Server Agent for Gluesync: Key Features

Index

Source data from MS SQL Server (via SQL Agent’s transaction logs)

Target MS SQL Server

Agent changelog

Troubleshooting

SQL Server source advanced settings

SQL Server target advanced settings

Core principles

This agent establishes a connection to MS SQL Server via a built-in JDBC driver.

Network protocol: TCP/IP

The Gluesync agent communicates with MS SQL Server exclusively over TCP/IP using the JDBC driver. Named Pipes is not used and is not required.

TCP/IP must be explicitly enabled in the SQL Server network configuration. In many default installations — particularly on Windows — only Named Pipes or Shared Memory may be active, which will prevent Gluesync from connecting.

To enable TCP/IP:

Open SQL Server Configuration Manager on the SQL Server host.
Navigate to SQL Server Network Configuration → Protocols for <your instance>.
Right-click TCP/IP and select Enable.
Restart the SQL Server service for the change to take effect.

For full instructions, refer to the official Microsoft documentation: Enable or Disable a Server Network Protocol (SQL Server Configuration Manager).

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.

Supported version

With this agent, you can target any version of MS SQL Server.

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.
Database pooling	✅	Supports connection pooling for efficient resource utilization across multiple pipelines.
Customizable isolation level	✅	Allows specifying the transaction isolation level (e.g., READ UNCOMMITTED, READ COMMITTED, REPEATABLE READ, or SERIALIZABLE) in the agent configuration to fine-tune concurrency and consistency.
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.

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.

Database pooling

✅

Supports connection pooling for efficient resource utilization across multiple pipelines.

Customizable isolation level

✅

Allows specifying the transaction isolation level (e.g., READ UNCOMMITTED, READ COMMITTED, REPEATABLE READ, or SERIALIZABLE) in the agent configuration to fine-tune concurrency and consistency.

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.

CDC via SQL Agent’s transaction logs

Works with MS SQL Server Server 2008 and above, hosted on-prem or in any DBaaS, SQL Azure as well. Only the Enterprise edition is supported, Standard from 2022 onwards.

Q&A

I have got MS SQL Server running under Microsoft Azure, is it supported? Microsoft Azure gives you the ability to obtain a fully managed instance of SQL Server called SQL Azure. SQL Azure is fully supported by Gluesync.