Forum Discussion
Microsoft Fabric Copy Job – SCD Type 2 (SCD2) Issues
Hi D4zk,
Since MERGE (SCD Type 1) is functioning while SCD Type 2 is not, this highlights the documented difference: SCD2 uses CDC-based historical tracking, including expiring rows and soft deletes, whereas MERGE updates only current data. SCD2 depends on CDC to handle inserts, updates, and deletes during incremental runs, so its behavior varies based on how those changes are applied. As your configuration has been validated, you can keep using MERGE for stability or consider submitting a support request for SCD2-specific issues.
Change data capture (CDC) in Copy Job - Microsoft Fabric | Microsoft Learn
Thank you for your response. I have verified all configurations and everything is correct. The issue is not related to edit mapping. When I stated that it should not be used, it was because I already understand what is happening. If I use MERGE instead of SCD Type 2, the flow executes successfully. This indicates that the root cause is related to the SCD Type 2 feature.
Hi D4zk,
Since MERGE (SCD Type 1) is functioning while SCD Type 2 is not, this highlights the documented difference: SCD2 uses CDC-based historical tracking, including expiring rows and soft deletes, whereas MERGE updates only current data. SCD2 depends on CDC to handle inserts, updates, and deletes during incremental runs, so its behavior varies based on how those changes are applied. As your configuration has been validated, you can keep using MERGE for stability or consider submitting a support request for SCD2-specific issues.
Change data capture (CDC) in Copy Job - Microsoft Fabric | Microsoft Learn