@kapa.ai can i use CT instead of CDC in MSSQL Source?

The knowledge sources do not explicitly address using CT (Change Tracking) as an alternative to CDC in the MSSQL source connector. These are two distinct SQL Server features: • CDC (Change Data Capture) — captures row-level changes by reading the transaction log and storing them in

cdc.*

change tables (e.g.,

cdc.dbo_<table>_CT

). • CT (Change Tracking) — a lighter-weight mechanism that only tracks which rows changed, not the full before/after data. Based on the knowledge sources, the Airbyte MSSQL source connector supports two replication methods: 1. Standard replication — uses

SELECT

queries with a cursor field; does not capture deletes. 2. CDC mode — uses Debezium to read SQL Server's CDC change tables (

cdc.*

schema). [MSSQL CDC forum] There is no mention of Change Tracking (CT) as a supported replication method in the Airbyte MSSQL connector. The connector's CDC implementation specifically reads from the

cdc.*

schema tables generated by SQL Server's CDC feature, not from Change Tracking. One related note: the

cdc

schema is currently excluded from the list of schemas Airbyte will expose for standard incremental syncs, meaning you cannot directly query the

cdc.*

change tables as a source stream either. [MSSQL CDC forum] If CT support is important to your use case, I'd recommend opening a GitHub issue on the Airbyte repository to request it as a feature. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.