Some of many tables in my mirror show a "running with warnings" message in Fabric Mirror Monitor.

[Anonymous]

We have setup mirroring to an AZ SQL database and that went just fine. Tables were initialised and replicated succesfullly. 

However, for the last few days I have noticed some tables are showing the "running with warnings" message in the mirror monitor and the last completed date is in the past and not consistant with the data in the source table. It appears changes are no longer being reflected into the mirror for those tables with warnings.

The message behind the bubble in monitor is not so reveling and simply states 'Internal system error occured. Artifactid = .....'

Our source AZ DB for the mirrored tables is configured with the Business Critical (BC_Gen5_12) SKU and does have a resonably heavy workload.

Can anyone help to shed some light on my issue.
@Anonymous @v-cboorla-msft 

[HimanshuS-msft]

I am also facing a simlar issue .

[Anonymous]

Yes I have done the stop and retart several times, forgot to mention that. After stop, start and long wait... it comes back up and looks ok but then within the next 24 hours some tables began to display the warning message again.

Also have already tried the queries you refer, plus another one that is recomended... and:

• sys.dm_change_feed_log_scan_sessions reveals nothing obvious
• nothing returned by sys.dm_change_feed_errors query
• EXEC sp_help_change_feed also shows nothing obvious

Restarting the service is not an viable option or a solution, as it takes 2-3 hours to complete initialising and within that period we would expect to have extracted multiple deltas to downstream processing and NRT is a requirement. i.e There is a service impact and we wont meet our agreed SLA.

Can we push this up to the Mirroring team for comment?

Regards

Tim

[Anonymous]

Hi @Anonymous 

Given the lack of enough information at this time, I can't tell what's causing your problem. You can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

The link of Power BI Support:  https://powerbi.microsoft.com/en-us/support/

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Fabric Community

Thank you for your understanding.

Best Regards

Zhengdong Xu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi @Anonymous 

Maybe you can try to restart Mirroring, sometimes, simply stopping and restarting the mirroring process can resolve transient issues. This will reinitialize the data from the source tables.

And you can use Dynamic Management Views (DMVs) and stored procedures to check for any errors in the change feed. You can run the following queries to diagnose issues:

-- Check change feed log scan sessions
SELECT * FROM sys.dm_change_feed_log_scan_sessions;

-- Check change feed errors
SELECT * FROM sys.dm_change_feed_errors;

Here are links for your reference:

Troubleshoot Fabric mirrored databases from Azure SQL Database (Preview) - Microsoft Fabric | Microsoft Learn

Frequently asked questions for Mirroring Azure SQL Database in Microsoft Fabric (Preview) - Microsoft Fabric | Microsoft Learn

Best Regards

Zhengdong Xu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.