Fabric Copy Job CDC Error On Incremental Load

Hi joel_delima​,

I would follow v-csrikanth​'s direction as well.

One additional point is that the successful initial load and the failing CDC runs use different read paths. Microsoft documents that the first Copy Job run performs a full load, while subsequent CDC runs read the SQL Server change feed, so success of the initial load does not necessarily validate the CDC path.

Microsoft currently lists on-premises SQL Server as a supported CDC source for Copy Job, but I do not see a published Fabric CDC support matrix that confirms behaviour for every historical SQL Server build.

Because both of your servers are SQL Server 2008 R2, I would compare more than just the major version:

• exact build / service pack level;
• database compatibility level;
• CDC capture instance metadata;
• table schema and data types;
• gateway version;
• permissions used by the Copy Job connection.

SQL Server 2008 R2 itself has been out of extended support for several years, so subtle differences between those two environments are worth checking.

The most useful next step is still to capture the exact statement that fails on the production server. Once you have that SQL, it should be much easier to determine whether the syntax is coming from the generated CDC query or from something specific to the source environment.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.