Disabling Change Tracking and enabling Change Data Capture in SQL Server Lakeflow

Upendra_Dwivedi — Tue, 11 Aug 2026 09:58:00 GMT

Hi All,

I want to know my lakeflow connect pipeline has stopped running because Change Tracking is enabled and table doesn't have a primary key and i want to switch to CDC now. Will it impact my pipeline. What are the steps i need to follow to on ingestion gateway and pipeline side.

Re: Disabling Change Tracking and enabling Change Data Capture in SQL Server Lakeflow

balajij8 — Tue, 11 Aug 2026 14:25:24 GMT

You can trigger a full refresh on this table to establish a clean CDC baseline. Pause the ingestion pipeline (and the gateway if running continuous Standard CDC) to prevent state conflicts while updating the source. Next, on the SQL Server instance, ensure CDC is enabled at the database level, then enable CDC on the target table. Because the table has no primary key, make sure the table CDC setup has net change support disabled, as supporting net changes requires a primary key or unique index. Once CDC is active on the table, explicitly disable Change Tracking on that table so Lake flow stops attempting to use it.

Before restarting the pipeline, verify through SQL Server system tables that the table reflects CDC as active and Change Tracking as disabled. Finally, re/start the gateway and pipeline, navigate to the table details within the Lake flow UI, and trigger a Full Refresh for the affected table so it can snapshot the current baseline and begin processing continuous CDC transactions seamlessly. Validate the changes in dev first. More details here

topic Disabling Change Tracking and enabling Change Data Capture in SQL Server Lakeflow in Data Engineering

Disabling Change Tracking and enabling Change Data Capture in SQL Server Lakeflow

Re: Disabling Change Tracking and enabling Change Data Capture in SQL Server Lakeflow