Back

Connectors

SQL Server Change Tracking

SQL Server Change Tracking is available as a replication method alongside CDC and log reading, without elevated permissions or direct log access.

Not every SQL Server environment allows full CDC or log access - especially in managed or restricted setups. For many teams, that’s meant choosing between limited replication options or overburdening DBAs just to enable streaming.

Artie now supports Change Tracking (CT) as a replication method, alongside CDC and T-SQL log reading. CT captures primary keys and version numbers for changed rows directly from SQL Server, enabling low-latency, incremental syncs without requiring elevated permissions or direct log access.

You can enable CT on selected tables, and Artie will automatically detect and replicate changes in near real time - maintaining the same reliability and consistency you expect from our streaming architecture.

Why this matters:

  • Lightweight replication with minimal database overhead
  • Works in restricted SQL Server environments where CDC/log access isn’t possible
  • Reduces dependency on DBAs and complex permissions
  • Maintains low-latency, reliable syncs across managed and hosted deployments
  • Expands deployment flexibility for diverse SQL Server environments

Learn more in our docs: SQL Server Change Tracking →

SQL Server change tracking docs