Forum Discussion
Fabric and SQL Azure Mirroring - duplicate data on Fabric side
Option 1 (unplug it and plug it back in) did the trick!
Is it a best practice with mirrored databases to periodically give them a restart like this?
Hi Anonymous thanks for the response. I don't have a screenshot of the Azure db, however if I create a dataflow in Fabric, you can see that the column 'TransferID' is the primary key, and if I use the 'Keep Duplicates' transformation on that column, it results in no rows (as expected). The db admin has also confirmed for me that there are no duplicates on the Azure side.
However, in the mirrored Fabric database of the same source, I created the same query to keep the duplicates, and there are multiple duplicated records as seen here:
The mirrored db is actively replicating, and not displaying any errors. I can see new records as recently as one minute ago. There are over 11M records in the table, with 38 duplicates, and each of the duplicates were created between April 19 - 23. We started replicating the db on April 16.
Hi jon_clemens , twhite_cargas
You can try the below steps:
1) Stop and restart Mirroring, this will reseed all the tables.. {the turn it off and on again option}
2) Better option, is to deselect this table in the Mirroring Configuration, save the configuration, then add the table back in again.
If the issue still persists then we need our internal team to investigate on this. So I request you to create a support ticket here: Microsoft Fabric Support and Status | Microsoft Fabric
After creating a Support ticket please provide the ticket number as it would help us to track for more information.
Hope this helps. Please let us know if you have any other queries.
Option 1 (unplug it and plug it back in) did the trick!
Is it a best practice with mirrored databases to periodically give them a restart like this?
Hi twhite_cargas
No - turning it off and on, moves all the data again. Its easy, but an expensive way to fix it.
The issue with duplicate rows might be happening due to a bug. Hence I have escalated the same, and our team is working on this to fix it.
ThanksHi Anonymous,
We're experiencing the same issue with our Fabric database mirror (duplicate records in the mirror, none in the source DB). Is there a further update on this issue?
Turning the replication off and the on again, as you've pointed out, is a time expensive exercise. It's also unclear when/how often this duplication occurs which makes managing the solution impractical.
Thanks
It is also happening on ourside. Any reason for the root cause?
