Changing a copy job destination

[TheFifthJoin]

How do I change the destination of a copy job? It seems like such a simple request I feel like I'm missing something obvious..

Long story short, I forgot to tick the collation button in my workspace before I created the lakehouse. There is no way to change the collation of a lakehouse post creation, so now I've ticked it, I'm in the process of moving everything in my bronze_lh to a staging lakehouse, so I can delete bronze_lh (created when collation was case sensitive), and create a new one with the same name now the collation on the workspace has been changed - then move everything back. (if anyone knows of a way to change the collation of an already created lakehoue that would save me this process please shout, but the collation documentation seems to be pretty set that you cant do it)

We're still fairly early on so its not too much of a hit. But, we do have a few copy jobs running that load data into our bronze_lh I'd just need to repoint - but there doesnt seem to be anything in the copy job that allows me to do that?

The menu only seems to let you edit source tables

The 'Destination' in the flow only opens the destination - no options to change

and the JSON is read only so while I can see the destination lakehouse ID, I can't change it.

Do I need to go through and recreate all of the copy jobs we've set up just to change the destination???

Note - this is for a copy job, not a copy job activity in a pipeline

[anilgavhane · Accepted solution]

@TheFifthJoin  Unfortunately, you cannot directly change the destination of an existing copy job once it's created. The UI only allows you to modify the source tables, not the target lakehouse or destination.

Recommended Workaround

Here’s what you can do:

1. Delete the Existing Copy Job
• Go to your Data Factory workspace in Fabric
• Locate the copy job under the “Data pipeline” or “Copy data” section
• Delete the job that points to the old lakehouse
2. Create a New Copy Job
• Use the same source tables
• Point the destination to your newly created lakehouse (with correct collation)
• Reapply any transformations or mappings you had in the original job
3. Optional: Use Pipelines for Flexibility

• If you want more control, consider using a Data Pipeline instead of a basic copy job
• Pipelines allow you to define dynamic parameters, making it easier to switch destinations in future

[TheFifthJoin]

I worried this was the case. Really surprised that level of basic editing for a job isn't available. I intentially used a copy job over a copy job activity as I've read its more efficient if you're just A-B copying and don't require any kind of transformation. Thanks for the reply, I best go start rebuilding copy jobs!