Live Monitoring of Fabric Mirroring
A current project called for mirroring a Google BigQuery dataset to Fabric. This feature is currently in private preview so don’t try to find it. However, the tips I share here should be applicable to other available mirroring scenarios, such as mirroring from Azure SQL Database.
One of the GBQ tables was a transaction fact table with some 130 million rows. The issue was that the mirroring window would show this table as normally replicating table with Running green status, but we waited and waited and nothing was happening…

First, the “Rows Replicated” counter is not continuously updating (doesn’t report live mirroring info). Instead, it’s updated when the table is fully replicated. That’s because the Delta table operations are atomic in nature.
So, how do we do live monitoring of the initial synchronization then? We can use the Azure Storage Explorer to access directly the delta files of the mirrored database as described here. After some experimenting (shorten the URL below to the workspace name only to see all OneLake artifacts in the workspace), I’ve found that the itemType of a mirrored database is MountedRelationalDatabase. So, the URL to an Adventure Works mirrored database in a workspace named Fabric Tutorial would be
https://onelake.dfs.fabric.microsoft.com/Fabric Tutorial/Adventure Works.MountedRelationalDatabase/
This lets us get to the underlying delta tables and delta logs in Azure Storage Explorer which are of course updating as data is being replicated. Examining the underlying storage is also useful to detect potential issues. Here is an example of the first table that was successfully replicated. Note that there is a parquet file containing the actual data.

And here is an example of the second table. As we can see, the delta log was created but there is no parquet file. So, something went wrong although according to Fabric all is well.

To summarize, the Fabric mirroring UI has left a lot of room for improvement. By examining the delta log file size and delta files of a specific table we can discover how the mirroring session of the initial synchronization is progressing.





Looking for easy ways to create intelligent bots or Retrieval-Augmented Generation (RAG) apps? 




