Stopping our Mirroring

Hi Louis_Legacyops 

Here are a few steps you can try to resolve this problem:

Check if your Fabric Capacity is stopped,

Execute the following stored procedure on your SQL Database to stop mirroring: 

exec sp_change_feed_disable_db;

Try these T-SQL queries to troubleshoot:

Execute the following query to check if the changes properly flow:

SELECT * FROM sys.dm_change_feed_log_scan_sessions;

If the sys.dm_change_feed_log_scan_sessions DMV doesn't show any progress on processing incremental changes, execute the following T-SQL query to check if there are any problems reported:

SELECT * FROM sys.dm_change_feed_errors;

If there aren't any issues reported, execute the following stored procedure to review the current configuration of the mirrored Azure SQL Managed Instance. Confirm it was properly enabled.

EXEC sp_help_change_feed;

 The key columns to look for here are the table_name and state. Any value besides 4 indicates a potential problem. (Tables shouldn't sit for too long in statuses other than 4)

If replication is still not working, verify that the correct SAMI object has permissions:
Troubleshoot Fabric Mirrored Databases From Azure SQL Managed Instance (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.