Edit

Share via


Frequently asked questions for Mirroring SQL Server in Microsoft Fabric

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

Features and capabilities

What authentication to the SQL Server is allowed?

Currently, for authentication to the source SQL Server, we support SQL authentication with user name and password and Microsoft Entra ID.

Is there a staging or landing zone for SQL Server? 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?

In the mirroring page of the Fabric portal, select the settings button, then select 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.

Self-help for Mirroring SQL Server in Microsoft Fabric

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

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

What are the replication statuses?

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 SQL Server database?

No, we just remove the streaming tables.

Can I mirror the same source database multiple times?

No, each SQL Server database can only be mirrored once. You just need a single copy of the data in Fabric OneLake, which you can share with others.

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

Yes, specific tables can be selected during Mirroring configuration.

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?

Fabric compute used to replicate your data into Fabric OneLake is free. The Mirroring storage cost is free up to a limit based on capacity. For more information, see Cost of mirroring and Microsoft Fabric Pricing. The compute for querying data using SQL, Power BI, or Spark is charged at regular rates.

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 concepts and licenses.

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 SQL Server?

If you're unable to Stop mirroring your SQL Server from the Fabric portal, or unable to delete your mirrored SQL Server item from Fabric, use the following steps.

  • In SQL Server 2025, execute the following stored procedure on your SQL Server database: EXEC sp_change_feed_disable_db;
  • In SQL Server 2016-2022, disable change data capture (CDC) using the following command: EXEC sys.sp_cdc_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 affect Mirroring and no data will be replicated.