Forum Discussion
The database cannot be mirrored to Fabric due Data Factory disabled
- 7 months ago
richard-aik I am glad that suggestion helped. If you have useful items in your original workspace that you want to replicate you may be able to do that using Git integration. If you have to move data, you'll need to use a copy job or activity for that.
Back to your original issue. Generally speaking, the fact that a workload's runtime is not available means the workspace cannot reach a Fabric capacity that runs all the runtimes. One trick you could try to save your workspace is to reassign the workspace to another capacity and then back. Sometimes some metadata gets corrupted behind the scene due to frequent Fabric updates especially if you did not touch the workspace for some time.If you find this answer useful or solving your problem please consider giving kudos and/or marking as a solution.
Thanks for looking at this issue together with me. I have the same F2 capacity assigned to both workspaces.
I also tried creating a new workspace to see if there's an enable/disable Data Factory option. (There's no such option).
With the same capacity licensing on both workspace. I don't understand why:
"Fabric Enginering Test Space" workspace mirroring + copyjob creation works, but
"F2 Development" workspace mirroring + copyjob failed ?
Here's the screenshot to show the same capacity level assigned.
Thanks and regards,
Richard