Copy Job: When Built-In State Management Beats Pipeline Plumbing

Copy Job: When Built-In State Management Beats Pipeline Plumbing Episode 12 • 2026-03-20 Duration: 9:54 Copy Job fills the gap between Mirroring's zero-config simplicity and Pipeline's full orchestration control. We break down the architecture, the 2x incremental pricing controversy, V-Order performance traps, and when you should still reach for Pipeline Copy Activity instead. What we discuss A real-world mistake from a pre-Fabric era The one question that reframes the architectural debate How we got here — predecessor products and evolution Why the "obvious" answer is often wrong A real Reddit/Microsoft Q&A question unpacked The concrete recommended architecture F-SKU realism — what this actually costs When the rejected approach is actually right Risks of the recommended path What Microsoft is shipping that changes the calculus The architectural principle to take home Key takeaways Take-home principle. Copy Job is Copy Activity with built-in memory. Same engine, same connectors — it just remembers where it left off. Start with a full load to validate your schema. Switch to incremental once you trust it. And always —... And that's the counterpoint to the counterpoint. Fair question. For a team that already has mature pipeline patterns — control tables, parameterized watermarks, solid error handling — that is a legitimate choice. You pay one-point-five CU across the board and get ForEach loops,... Resources Copy Job Connectors CDC Replication Connectors VNet Data Gateway for Copy Job CI/CD for Copy Job Copy Job Activity What is Copy Job in Data Factory? Create a Copy Job Quickstart: Create a Copy Job CDC in Copy Job (Preview) Copy Job Pricing Monitor a Copy Job Data Movement Decision Guide Data Integration Decision Guide What is Data Factory in Fabric? Pricing Scenario: Copy Job 1 TB CSV to Lakehouse About the show Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon. Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday. Submit your case Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing. Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.