Mirrored Azure SQL Database

[Anonymous]

I have set up a staging area on an Azure SQL Server where tables are refreshed every night/morning by first being emptied and then refilled with new data. I have created a Mirrored Azure SQL database connection in Fabric for these tables. The connection works perfectly the first time, but the next day I encounter the following error message (screenshot attached).

It seems that the mirror is not being re-established after the tables are refreshed. Could anyone provide insights on why this might be happening and what steps I can take to resolve this issue?

Thank you in advance for your assistance!

[Anonymous · Accepted solution]

We are performing a truncate on the table, but this issue still persists. I have now created a pipeline that turns the mirror off and on again every morning. This works well.

[nilendraFabric]

Hello @Anonymous 

When the tables in your Azure SQL Database are emptied and refilled, they may be dropped and recreated. This can disrupt the mirroring process because the mirrored database in Fabric may lose track of the original tables

Ensure that tables are not being dropped and recreated during the refresh process. Instead of dropping tables, truncate them using TRUNCATE TABLE to preserve their schema and metadata, which helps maintain mirroring continuity