Forum Discussion
Copy Job Not Updateble ?
- 6 months ago
Hi Fiodar , one thing I can say is the copy job are not one-time jobs, and it seems like you are facing an issue with your copy job configuration, from the image you sent I can't tall you much about but as an experienced developer in fabric data factory, a copy from SQL to SQL is very straight forward... are both the source and target on prem-sql databases? in the image everything seems to worked fine, but you don't see any data at the target? is that the issue? If you provide more information, I think me or more poeple in the community can help 😁 ... you can share the pipeline code and I can test on my side and see what is wrong if you like.... looking forward, all the best.
- 6 months ago
Hi Fiodar , Thank you for reaching out to the Microsoft Community Forum.
A Fabric Copy job is not a pipeline. When you create it, the selected tables are locked into the job definition. You can rerun it, but you cannot add or remove tables afterward. That’s why you can’t add a single table now. If you need different or additional tables, you must create a new Copy job or switch to a Data Factory pipeline, which supports dynamic table selection.
Hi Fiodar , Thank you for reaching out to the Microsoft Community Forum.
A Fabric Copy job is not a pipeline. When you create it, the selected tables are locked into the job definition. You can rerun it, but you cannot add or remove tables afterward. That’s why you can’t add a single table now. If you need different or additional tables, you must create a new Copy job or switch to a Data Factory pipeline, which supports dynamic table selection.