Fabric database is mirrored to another warehouse

Hi @Angelo Spaziani

Thank you for the additional details.

Since you're receiving**"The database has already been mirrored on another Fabric warehouse"**, and you've mentioned that the database may have been mirrored previously through a Fabric trial, this could indicate that stale mirroring metadata still exists for the source database.

Before taking any cleanup actions, could you please check the following from the source Azure SQL Database:

SELECT * FROM sys.dm_change_feed_log_scan_sessions;
SELECT * FROM sys.dm_change_feed_errors;
EXEC sp_help_change_feed;

In the sp_help_change_feed output, please review the table_name and state columns. Any state other than 4 may indicate a mirroring configuration issue.

In addition, please verify with your Fabric administrator that:

• The tenant setting**"Users can access data stored in OneLake with apps external to Fabric"** is enabled.
• The Fabric capacity and workspace are active and not paused or deleted.
• The Azure SQL Server System Assigned Managed Identity (SAMI) has the appropriate permissions on the mirrored database item.

Regarding the account still appears to be associated with a trial even though you have a paid Fabric subscription, it would also be helpful to confirm whether the original trial workspace is still present in the tenant, as an orphaned mirroring configuration from that workspace could be contributing to the issue.

Please share the results of the above queries and any additional error details, and we'll be happy to assist further.

Note: We do not recommend running EXEC sp_change_feed_disable_db unless there is a confirmed need to permanently remove an existing mirroring configuration, as this disables the current change feed configuration and requires mirroring to be recreated from scratch.

Please let us know if you have any questions or concerns.