Fabric database is mirrored to another warehouse

Angelo Spaziani 0 Reputation points

I am getting an error that states a DB I'm trying to mirror is attached to another warehouse. I believe this is related to an azure fabric trial I started a few months ago. I have no access to any other workspaces to unlink the existing mirror.

  1. Manish Deshpande 7,010 Reputation points • Microsoft External Staff • Moderator

    Hello @Angelo Spaziani

    We are looking into the issue and we will get back to you shortly with an update.

  2. Angelo Spaziani 0 Reputation points

    Thank you, it looks like my account is still marked as a trial. When I try to create a pipeline it says I need to upgrade, I already have a paid Fabric subscription.

  3. Manoj Kumar Boyini 17,060 Reputation points • Microsoft External Staff • Moderator

    Hi @Angelo Spaziani

    I kindly request you to please share the details requested in the private message for further investigation.

  4. Angelo Spaziani 0 Reputation points

    It looks like the issue with creating pipelines is resolved. I'm still unable to mirror a DB due to the issue above.

  5. Angelo Spaziani 0 Reputation points

    @Manish Deshpande have you had any luck getting this issue resolved?

Sign in to comment

1 answer

  1. Manoj Kumar Boyini 17,060 Reputation points • Microsoft External Staff • Moderator

    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.

    1. Angelo Spaziani 0 Reputation points

      dm_change_feed_log_scan_sessions yields no results.

      dm_change_feed_errors, yields a bunch of errors for "Error occurred while interacting with landing zone."

      Everything from EXEC sp_help_change_feed; has a state of 7.

      i am the fabric admin. this was already setup previously in another workspace i no longer have access to because it was removed, not due to permissions. i need to recreate the mirror.

    Sign in to comment
Sign in to answer

Your answer