Forum Discussion
SQL Server Mirroring keeps giving error when I want to add more tables
Hi sholy29
Thank you for the detailed update and the screenshot.The error message “Test connection failed. The Data Factory runtime is busy now. Please retry the operation later” shows that the issue is now due to a runtime resource contention in Microsoft Fabric’s backend, specifically the Data Factory runtime that manages mirroring and data movement. This usually happens when there are many concurrent operations, like active mirroring or data transformation jobs, which can temporarily use up available resources.
To address this, it’s recommended to wait 15–30 minutes and then try again, as these issues often resolve themselves. Also, try to avoid running overlapping workloads at the same time pause any active pipelines, Dataflows, or Power BI dataset refreshes if possible.
Additionally, If you have access, use a dedicated Fabric capacity workspace, since lower SKUs or trial capacities are more likely to encounter this issue. You might also try using a new browser session or incognito window to prevent session token problems. For authentication, using a linked service with a stored SQL username and password is valid for mirroring, so no changes are needed there.
Thank you for being part of Fabric Community Forum.
Regards,
Karpurapu D,
Microsoft Fabric Community Support Team.
Community SupportHi sholy29
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Thank you.
However, the error still occur. Previously, I activated CDC for all tables and entity in the SQL Server database. Based on your recommendation, I thought I must have actived CDC on an unsupported schema elements.
I went back and only activated CDC on the selected modules/table that I need to mirror. I though this would have resolved it and I was wrong. I still get the error. See below for screenshot.
I doubt if it is gateway misconfigurations because, when I use Dataflow Gen 2 or Copy Job to copy table from our sql server, I do not get this error.
What do you mean by "Ensure SQL authentication is used for connectivity". We currently use an Azure linked services as our username and password to connect to our on-prem sql server
What you do recomend. Thanks
- v-karpurapud
Hi sholy29
Thank you for the detailed update and the screenshot.The error message “Test connection failed. The Data Factory runtime is busy now. Please retry the operation later” shows that the issue is now due to a runtime resource contention in Microsoft Fabric’s backend, specifically the Data Factory runtime that manages mirroring and data movement. This usually happens when there are many concurrent operations, like active mirroring or data transformation jobs, which can temporarily use up available resources.
To address this, it’s recommended to wait 15–30 minutes and then try again, as these issues often resolve themselves. Also, try to avoid running overlapping workloads at the same time pause any active pipelines, Dataflows, or Power BI dataset refreshes if possible.
Additionally, If you have access, use a dedicated Fabric capacity workspace, since lower SKUs or trial capacities are more likely to encounter this issue. You might also try using a new browser session or incognito window to prevent session token problems. For authentication, using a linked service with a stored SQL username and password is valid for mirroring, so no changes are needed there.
Thank you for being part of Fabric Community Forum.
Regards,
Karpurapu D,
Microsoft Fabric Community Support Team.- v-karpurapud
Hi sholy29
We have not yet heard back from you about whether our response addressed your query. If it did not, please share more details so we can assist you more effectively.
Thank You.