Forum Discussion

tim_goodsell's avatar
tim_goodsell
Frequent Visitor
3 months ago
Solved

Fabric Mirrored Databases

I have just va couple of questions about fabroc mirrored databases   When i stop the replication all monitoring data disappears, when i start it again monitoring data appears but the last complete ...
data hub
  • svenchio's avatar
    svenchio
    3 months ago

    But, did you check the status using the API? according to the current documntation, at table-level, there is not sucha "Running", see from current oficial doc.  Mirroring - Get Tables Mirroring Status - REST API (MirroredDatabase) | Microsoft Learn  ... in my article Removing Orphan Fabric Deployment Pipelines follow pre-requisites and solution steps 1 (get access token) & 2 (post-man auth) and issue a Post request to the interface replacing Ids as corresponding 

    https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/mirroredDatabases/{mirroredDatabaseId}/getTablesMirroringStatus

     

    And check the status of the tables, what is the actual status of the tables? 

     

     

    Let us know! 

svenchio's avatar
svenchio
Super User
3 months ago

Hi  tim_goodsell , the answer to "is the mirrored database being synchronised again?" is Yes, when you stop replication, the monitoring metrics/history are cleared, when replication restarts, Fabric resumes synchronisation and monitoring from the current state, so the “last completed” timestamp gets updated as replication catches up.

 

To determine when replication has fully completed, the best approach is to monitor the replication lag/status via API's rather than relying on data arrival in the landing zone, I'm thinking that there's an orchestration that could query the API, if so, use  Mirroring - Get Mirroring Status - REST API (MirroredDatabase) | Microsoft Learn   to get the status of the mirrored database and make sure replication is Running;  use Mirroring - Get Tables Mirroring Status - REST API (MirroredDatabase) | Microsoft Learn  for a specific table(s); Use Replicating it is the status you want to wait for before downstream processing starts, because it means the initial snapshot has completed and CDC replication is active.

 

Hope it helps, if you find useful a thumb-up would be nice and if this information solved your issue, mark as solution. Best of lucks! 

 

 

tim_goodsell's avatar
tim_goodsell
Frequent Visitor
3 months ago

Thanks for that, looking at the monitor replication screen the status is 'running' and for each table the status is 'running', does this mean the tables are still being currently updated or is it in a ready stage waiting for new files to landed in the landing zone before the mirrored database is updated.