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

This article answers frequently asked questions about Mirroring Azure SQL Database in Microsoft Fabric.

Features and capabilities

What authentication to the Azure SQL Database is allowed?

Currently, for authentication to the source Azure SQL Database, we support SQL authentication with user name and password, Microsoft Entra ID, and Service Principal.

Is there a staging or landing zone for Azure SQL Database? If so, is it outside of OneLake?

A landing zone in OneLake stores both the snapshot and change data, to improve performance when converting files into delta verti-parquet.

How long does the initial replication take?

It depends on the size of the data that is being brought in.

How long does it take to replicate inserts/updates/deletes?

Near real-time latency.

Do you support replicating of views, transient or external tables?

No. Currently, only replicating regular tables are supported.

How do I manage connections?

Select the settings cog, then select on Manage connection and gateways. You can also delete existing connections from this page.

Can Power BI reports on mirrored data use direct lake mode?

Yes, since tables are all v-ordered delta tables.

Troubleshoot Mirroring Azure SQL Database in Microsoft Fabric

How do I know Fabric is replicating data on my Azure SQL Database?

If you're experiencing mirroring problems, perform the following database level checks using Dynamic Management Views (DMVs) and stored procedures to validate configuration. Contact support if troubleshooting is required.

  1. Execute the following query to check if the changes properly flow:
    SELECT * FROM sys.dm_change_feed_log_scan_sessions 
    

For troubleshooting steps, see Troubleshoot Fabric mirrored databases from Azure SQL Database.

How to enable System assigned managed identity (SAMI) on SQL Server?

What are the replication statuses?

Can Azure SQL Database Mirroring be accessed through the Power BI Gateway or behind a firewall?

Currently, access through the Power BI Gateway or behind a firewall is unsupported.

What steps does restarting the Mirroring include?

The data from source tables will be reinitialized. Each time you stop and start, the entire table is fetched again.

What happens if I remove a table from Mirroring?

The table is no longer replicated and its data is deleted from OneLake.

If I delete the Mirror, does it affect the source Azure SQL database?

No, we just remove the streaming tables.

Can I mirror the same source database multiple times?

Yes, you can, but you shouldn't need to. Once the data is in Fabric, it can be shared from there.

Can I mirror only specific tables from my Azure SQL database?

Yes, specific tables can be selected during Mirroring configuration.

What happens to Mirroring in an event of planned or unplanned Geo failover?

Mirroring is disabled in an event of geo failover, whether planned or unplanned, as there are potential data loss scenarios. If this occurs, create a new mirror and configure it to point to the new logical SQL server and Azure SQL Database.

Security

Is data ever leaving the customers Fabric tenant?

No.

Is data staged outside of a customer environment?

No. Data isn't staged outside of customer environment, it's staged in the customer's OneLake.

Cost Management

What are the costs associated with Mirroring?

During preview, there's no cost for Mirroring or storing mirrored data in Fabric. Cost of the source Azure SQL Database is separate from Fabric Mirroring.

What do we recommend a customer do to avoid or reduce Azure SQL Database costs?

See Plan and manage costs for Azure SQL Database. Consider using a dedicated, smaller Azure SQL Database, based on requirements.

How are ingress fees handled?

Fabric doesn't charge for Ingress fees into OneLake for Mirroring.

Licensing

What are licensing options for Fabric Mirroring?

A Power BI Premium, Fabric Capacity, or Trial Capacity is required. For more information on licensing, see Microsoft Fabric licenses.

How are egress fees handled?

If the Azure SQL Database is located in a different region from your Fabric capacity, data egress will be charged. If in the same region, there is no data egress.

Stop or pause Fabric Mirroring

What are the results of stopping Mirroring?

Replication stops in the source database, but a copy of the tables is kept in OneLake. Restarting the mirroring results in all data being replicated from the start.

How to stop/disable Mirroring from your Azure SQL Database?

If you're unable to Stop mirroring your Azure SQL Database from the Fabric portal, or unable to delete your mirrored Azure SQL database item from Fabric, execute the following stored procedure on your Azure SQL Database: exec sp_change_feed_disable_db;

What if I stop or pause my Fabric capacity?

The Fabric capacity needs to be active and running. A paused or deleted capacity will impact Mirroring and no data will be replicated.