{"id":105089,"date":"2025-01-15T19:44:51","date_gmt":"2025-01-15T19:44:51","guid":{"rendered":"https:\/\/www.red-gate.com\/simple-talk\/?p=105089"},"modified":"2025-01-15T19:57:41","modified_gmt":"2025-01-15T19:57:41","slug":"fabric-copy-job-whats-new-in-it","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/blogs\/fabric-copy-job-whats-new-in-it\/","title":{"rendered":"Fabric Copy Job: What’s new in it"},"content":{"rendered":"

At first sight, the new Copy Job may seem only one more redundancy: Why do we need this?<\/p>\n

We have Data Pipelines for the Copy Activity and also a Copy Assistant to help us configure it. What’s new about the Copy Job?<\/p>\n

Spoiler:<\/strong> It’s much more than a new UI<\/p>\n

<\/p>\n

The new Copy Job Object and UI<\/h2>\n

The Copy Job is exactly what the name says: a “dedicated data pipeline” intended only to execute a copy activity. We schedule it exactly as a data pipeline.<\/p>\n

The new UI is cute, you finish the configuration with the job already scheduled for every 15 minutes by default.<\/p>\n

\"A<\/p>\n

These are only the small details.<\/p>\n

Incremental Load with the Copy Job<\/h2>\n

In my opinion, this is the great advantage of this new feature: It builds an incremental load for you.<\/p>\n

The configuration for incremental load requires an incremental column. A date\/time column which will allow the job to identify changed records.<\/p>\n

The source model is the responsible for updating the date\/time column every time a record is updated. After that, the job manages all the work.<\/p>\n

\"A<\/p>\n

The job will make a first execution with a full load, and continue with incremental load every 15 minutes, by default.<\/p>\n

Copy Job and Other Options<\/h2>\n

How this new feature compare with the other options?<\/p>\n

We have the CDC Ingestion from Azure SQL<\/a> and Mirroring from Azure SQL<\/a>, how the new job compares with them?<\/p>\n

Let’s enumerate some differences:<\/p>\n