Forum Discussion
Azure SQL DB mirroring issue
Hi,
We tried mirroring our azure sql database on fabric. On first attempt, it worked fine but the sync has stopped from next day. When we try to configure the replication, we are facing below errors
Our SAMI is enabled and it should not be an issue. We are not sure why this is happening.
Please post a solution if there is anyone faced this before.
Hi Sravanthi1901 ,
Thank you for sharing the details. It seems like you're encountering issues with maintaining the replication between your Azure SQL database and Fabric after the initial successful sync.
Based on the errors you've listed, here are a few suggestions to consider:
- Source Connection Unknown: Double-check that the source database still exists and that the connection string or linked service hasn't changed or expired.
- Permissions: Ensure that the identity used for the connection (especially if using a managed identity) has the necessary permissions on both the source and target environments.
- Managed Identity Retrieval Failure: This could be related to a temporary issue with Azure AD or a misconfiguration in the Fabric environment. Try re-authenticating or reassigning the managed identity.
- Activity ID Undefined: This might indicate a deeper issue in the Fabric service or a bug. Reviewing the diagnostic logs or raising a support ticket with Microsoft might help.
Since your SAMI is enabled, it might be worth verifying that it is correctly assigned and has the right roles (e.g., SQL Server Contributor, Reader, etc.).
If anyone has encountered a similar issue and found a resolution, your insights would be greatly appreciated.
4 Replies
Hi Sravanthi1901,
Thank you for reaching out to Microsoft Fabric Community Forum.
Can you please check if the Microsoft Fabric Data service principal has the Reader or Managed Identity Operator role assigned on your Azure SQL Server?
Even with SAMI enabled, missing this permission can cause the error you're seeing in Fabric.A similar issue has been a known problem on Microsoft’s end, though this case is slightly different. If the role is already assigned and you're still seeing the error, I recommend raising a support ticket for deeper investigation.
Below is the link to create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticketIf this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Regards,
Vinay PabbuHi Sravanthi1901 ,
Thank you for sharing the details. It seems like you're encountering issues with maintaining the replication between your Azure SQL database and Fabric after the initial successful sync.
Based on the errors you've listed, here are a few suggestions to consider:
- Source Connection Unknown: Double-check that the source database still exists and that the connection string or linked service hasn't changed or expired.
- Permissions: Ensure that the identity used for the connection (especially if using a managed identity) has the necessary permissions on both the source and target environments.
- Managed Identity Retrieval Failure: This could be related to a temporary issue with Azure AD or a misconfiguration in the Fabric environment. Try re-authenticating or reassigning the managed identity.
- Activity ID Undefined: This might indicate a deeper issue in the Fabric service or a bug. Reviewing the diagnostic logs or raising a support ticket with Microsoft might help.
Since your SAMI is enabled, it might be worth verifying that it is correctly assigned and has the right roles (e.g., SQL Server Contributor, Reader, etc.).
If anyone has encountered a similar issue and found a resolution, your insights would be greatly appreciated.
Thank you for the quick response. We have provided necessary permissions for the identity used for the connection and it worked fine.
Thanks
Hi burakkaragoz Anonymous
Source Connection Unknown issue: We have noticed that who ever has created the mirrored database, only they are able to see the connection properly. If some one access the same work space who has equal permissions are not able to see the Source Connection. Is this how it works or do we need to provide additional permissions for users who uses the same workspace to see the source connection?
Thanks,
Sravanthi
