Forum Discussion
Error with SQL DB Mirroring to Fabric
Hi jkerber,
Ensure that only user-defined tables are selected for mirroring, and explicitly exclude system-generated tables, especially those under the cdc schema or with names like MSchange_tracking. These are internal metadata tables used by SQL Server for Change Tracking or CDC and are not meant to be mirrored.Double-check that the database context and schema are correctly set in your mirroring configuration, as misalignment here can cause errors. If retrying replication on individual failed tables shows them as valid, it confirms the issue is schema-level, not data-level.
Avoid including any internal SQL Server metadata tables in the replication set. Review your gateway setup and mirroring configuration to include only the necessary user tables.
If the issue persists, try manually replicating a few failing tables and consider temporarily disabling CDC, mirroring the tables, and then re-enabling CDC after successful replication.
I'm attaching the official Microsoft documents for your review, This might help you:
Microsoft Fabric Mirrored Databases From SQL Server - Microsoft Fabric | Microsoft Learn
Troubleshoot Fabric Mirrored Databases - Microsoft Fabric | Microsoft Learn
Limitations of Fabric Mirrored Databases From SQL Server - Microsoft Fabric | Microsoft Learn
The Microsoft community is here to assist you. Thank you, and please continue using the Forum.Regards,
Community Support Team.
Community SupportHi jkerber,
Ensure that only user-defined tables are selected for mirroring, and explicitly exclude system-generated tables, especially those under the cdc schema or with names like MSchange_tracking. These are internal metadata tables used by SQL Server for Change Tracking or CDC and are not meant to be mirrored.
Double-check that the database context and schema are correctly set in your mirroring configuration, as misalignment here can cause errors. If retrying replication on individual failed tables shows them as valid, it confirms the issue is schema-level, not data-level.
Avoid including any internal SQL Server metadata tables in the replication set. Review your gateway setup and mirroring configuration to include only the necessary user tables.
If the issue persists, try manually replicating a few failing tables and consider temporarily disabling CDC, mirroring the tables, and then re-enabling CDC after successful replication.
I'm attaching the official Microsoft documents for your review, This might help you:
Microsoft Fabric Mirrored Databases From SQL Server - Microsoft Fabric | Microsoft Learn
Troubleshoot Fabric Mirrored Databases - Microsoft Fabric | Microsoft Learn
Limitations of Fabric Mirrored Databases From SQL Server - Microsoft Fabric | Microsoft Learn
The Microsoft community is here to assist you. Thank you, and please continue using the Forum.
Regards,
Community Support Team.
- v-sgandrathi
Hi jkerber,
We wanted to check if you had a chance to review our last reply. Let us know if it helped or if you need more guidance, we're always happy to help further.
If the solution worked for you, please click Accept as Solution and feel free to leave a Kudos for visibility.
Looking forward to hearing from you!
- v-sgandrathi
Hi jkerber,
I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.
If our response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.
Thank you.
- v-sgandrathi
Hi jkerber,
Just wanted to check regarding your question. We haven’t heard back and want to ensure you're not stuck. If you need anything else or have updates to share, we’re here to help!
If the previous reply resolved your issue, please consider marking it as Accepted and giving it a Kudos to help others find it easily.
If it's resolved, feel free to hit Accept as Solution and drop a Kudos.