When to Use Pre-Copy Script vs. Source Query in Copy Activity?

[HamidBee]

Hello everyone,

I’m trying to get a better understanding of the Pre-Copy Script option in Microsoft Fabric's Copy Activity. Given that we already have the option to use a query to pull data from the source, I’m curious about the specific situations where the Pre-Copy Script comes in handy. Is it generally an either/or choice between using a query and a pre-copy script, or are there scenarios where it makes sense to use both within the same activity?

If anyone here actively uses the Pre-Copy Script, I’d love to hear about your experiences and the types of use cases where it’s proven helpful.

Thanks in advance!

[MonicaCVL]

Hi @HamidBee 

The Pre-Copy Script in Microsoft Fabric’s Copy Activity is useful for tasks like cleaning up old data, making schema adjustments, preparing data, or implementing conditional logic before copying new data. It can be used alongside a query to ensure both the source data and destination environment are properly managed.

with regards

Monica CVL

[FabianSchut · Accepted solution]

The difference between the query and the pre-copy script is that the query is performed on the source, while the pre-copy script is performed on the destination. You can use both within the same activity. You could for example delete all the records from the destination before you write new rows from the source to the destination that you've selected with your query.