A common scenario when using Mirroring in Fabric for Azure SQL Database is when everything appears healthy, yet no data is actually replicated.
In this situation:
- The Fabric portal shows the mirror status as Running
- Tables are visible in the mirrored database
- No explicit errors are displayed in the Fabric UI
- Row counts remain at zero
This blog walks through a real-world troubleshooting scenario where mirroring looked healthy on the surface, but replication never started.
Investigating the Issue
When troubleshooting Fabric mirroring issues from this link Troubleshooting steps for mirroring issues, we found out in last step for permission issues. Copy pasted key steps here
The root cause was a permission issue. The Fabric identity (service principal or managed identity) did not have the required Read + Write permissions on the mirrored database item in Microsoft Fabric.
Resolution
Once the issue was identified, the fix was straightforward:
- Open the Microsoft Fabric portal
- Navigate to the mirrored Azure SQL Database item
- Select Manage permissions
- Grant Read + Write permissions to the Fabric service principal / managed identity
Result
After correcting the permissions:
- Snapshot initialization completed successfully
- Data replication resumed automatically
- Rows began populating in the Fabric mirrored database
Disclaimer: Please be aware that the products and options discussed in this article are subject to change. This article discusses Mirrored Azure SQL Database Not Replicating in Microsoft Fabric scenario.
References:
Troubleshoot Fabric Mirrored Databases From Azure SQL Database - Microsoft Fabric | Microsoft Learn
Database Engine events and errors (22000 to 22999) - SQL Server | Microsoft Learn
Microsoft Fabric Mirrored Databases from Azure SQL Database - Microsoft Fabric | Microsoft Learn
https://learn.microsoft.com/en-us/fabric/mirroring/azure-sql-database-troubleshoot
Microsoft