Forum Discussion
Mirrored Azure SQL Database Won't Mirror
- 1 year ago
Hi mattke2b ,
If you have verified everything related to SAMI and is functioning as expected Please try the below steps nowDo not remove Azure SQL Database service principal name (SPN) contributor permissions on Fabric mirrored database item.
If you accidentally remove the SPN permission, Mirroring Azure SQL Database will not function as expected. No new data can be mirrored from the source database.
If you remove Azure SQL Database SPN permissions or permissions are not set up correctly, use the following steps.
- Add the SPN as a user by selecting the
...ellipses option on the mirrored database item. - Select the Manage Permissions option.
- Enter the name of the Azure SQL Database logical server name. Provide Read and Write permissions.
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thank you - Add the SPN as a user by selecting the
Hi mattke2b ,
Thanks for reaching out to the Microsoft fabric community forum.
After enablement, if SAMI setting status is either turned Off or initially enabled, then disabled, and then enabled again, the mirroring of Azure SQL Database to Fabric OneLake will fail.
The SAMI must be the primary identity. Verify the SAMI is the primary identity with the following: SELECT * FROM sys.dm_server_managed_identities;
User Assigned Managed Identity (UAMI) is not supported. If you add a UAMI, it becomes the primary identity, replacing the SAMI as primary. This causes replication to fail. To resolve:
Remove all UAMIs. Verify that the SAMI is enabled.
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thank you