Fabric Copy Job CDC Error On Incremental Load

Hi joel_delima​

The successful initial load confirms that Copy Job can read the table, but subsequent CDC runs use a different read path. The error alone doesn’t identify the failing SQL statement, so it isn’t enough to confirm a problem with the SQL generated by Copy Job.

To isolate the cause:

1. Capture the failing SQL on production. With your DBA’s approval, use SQL Server Profiler/SQL Trace for SQL Server 2008 R2. Filter narrowly to the Copy Job login and source database, and capture SQL:BatchStarting, RPC:Starting, Exception, and User Error Message, including SQL text and session ID. Run one incremental copy and stop the trace immediately afterward. This should help correlate the syntax error with the submitted statement.
2. Compare the exact configurations—not just the server versions. Check engine builds/service packs, database compatibility levels, database/schema/table/column names, CDC capture instances, and Copy Job source settings and mappings. Differences in identifiers or CDC configuration are worth investigating, but shouldn’t be treated as the cause until the captured SQL confirms it.
3. Base the fix on that statement. Have the DBA inspect the failing SQL, particularly identifier qualification and quoting around the reported .. Avoid renaming production objects or disabling/re-enabling CDC without a confirmed diagnosis. If the statement points to a generated-query issue, raise a Fabric Support case with the captured SQL, run/activity ID, and failure timestamp.

Thank you.