Mirroring Error

[lfparaujo]

Hello team, I've been trying to mirror a SQL on-premises to a Fabric Workspace but it is showing an internal error.

Already checked the configuration in the data gateway, everything is ok.

Can you guys help me with this?

[v-karpurapud]

Hi @lfparaujo 

I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.

Thank you.

[v-karpurapud]

Hi @lfparaujo 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-karpurapud]

Hi @lfparaujo 

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[lfparaujo]

Hello @gslick I've just tried and it showed another Internal error. 
this is a contoso database, I believe all the tables have primary keys.

[v-karpurapud]

Hi @lfparaujo 

Just wanted to know if you have tried my suggestions. if you did, can you please share the details, for us to better understand the issue. If not, can you please try them and share the outcome.


Thank you.

[v-karpurapud · Accepted solution]

Hi @lfparaujo 

Welcome to the Microsoft Fabric Forum. Also, thank you @gslick for your response.
 

The "Internal System Error” encountered during SQL Server mirroring in Microsoft Fabric usually indicates a platform-level issue rather than a user misconfiguration, especially if gateway settings have been verified. This error, often accompanied by codes such as a mirror artifact ID, suggests an internal service disruption or compatibility conflict.

Check the Microsoft Fabric service status through the or the Azure Service Health dashboard. Even if no outage is reported, these errors can result from transient backend issues, and retrying after 15–30 minutes can often resolve the problem without intervention.

Ensure the on-premises SQL Server environment meets Fabric’s compatibility requirements. Also, verify that SQL Server is version 2016 or later, that TCP/IP is enabled, and that the connection uses SQL authentication. Deprecated features such as TEXT, NTEXT, IMAGE, or unsupported data types may also cause replication failures. It is recommended to inspect the schema for these data types and run a DBCC CHECKDB command to confirm the database integrity.

Even the gateway configuration may appear correct, it may be useful to restart the on-premises data gateway service and revalidate the data source settings in the Power Platform admin center. Rebinding the data source in Microsoft Fabric and testing the connection can help eliminate any hidden connectivity issues.

If the issue persists after these steps, consider deleting and recreating the mirrored database, starting with a small subset of tables to isolate any schema-related problems.

If this response resolves your query, kindly mark it as Accepted Solution to help other community members. A Kudos is also appreciated if you found the response helpful.

Thank You!

[gslick]

I have never tried it from on premise , I have always do it from azure sql database. Do the tables you are trying to replicate have primary keys? Have you tried to replicate a very simple table with 2 columns and e.g Pkid (int), testcolumn varchar(50) ?