Mirroring Azure SQL Database

Mirroring in Fabric provides an easy experience to avoid complex ETL (Extract Transform Load) and integrate your existing Azure SQL Database estate with the rest of your data in Microsoft Fabric. You can continuously replicate your existing Azure SQL Databases directly into Fabric's OneLake. Inside Fabric, you can unlock powerful business intelligence, artificial intelligence, Data Engineering, Data Science, and data sharing scenarios.

For a tutorial on configuring your Azure SQL Database for Mirroring in Fabric, see Tutorial: Configure Microsoft Fabric mirrored databases from Azure SQL Database.

To learn more and watch demos of Mirroring Azure SQL Database in Fabric, watch the following the Data Exposed episode.

Why use Mirroring in Fabric?

With Mirroring in Fabric, you don't need to piece together different services from multiple vendors. Instead, you can enjoy a highly integrated, end-to-end, and easy-to-use product that is designed to simplify your analytics needs, and built for openness and collaboration between Microsoft, Azure SQL Database, and the 1000s of technology solutions that can read the open-source Delta Lake table format.

What analytics experiences are built in?

Mirrored databases are an item in Fabric Data Warehousing distinct from the Warehouse and SQL analytics endpoint.

Mirroring creates three items in your Fabric workspace:

• The mirrored database item. Mirroring manages the replication of data into OneLake and conversion to Parquet, in an analytics-ready format. This enables downstream scenarios like data engineering, data science, and more.
• A SQL analytics endpoint
• A default semantic model

Each mirrored Azure SQL Database has an autogenerated SQL analytics endpoint that provides a rich analytical experience on top of the Delta Tables created by the mirroring process. Users have access to familiar T-SQL commands that can define and query data objects but not manipulate the data from the SQL analytics endpoint, as it's a read-only copy. You can perform the following actions in the SQL analytics endpoint:

• Explore the tables that reference data in your Delta Lake tables from Azure SQL Database.
• Create no code queries and views and explore data visually without writing a line of code.
• Develop SQL views, inline TVFs (Table-valued Functions), and stored procedures to encapsulate your semantics and business logic in T-SQL.
• Manage permissions on the objects.
• Query data in other Warehouses and Lakehouses in the same workspace.

In addition to the SQL query editor, there's a broad ecosystem of tooling that can query the SQL analytics endpoint, including SQL Server Management Studio (SSMS), the mssql extension with Visual Studio Code, and even GitHub Copilot.

Network requirements

Currently, Mirroring doesn't support Azure SQL Database logical servers behind an Azure Virtual Network or private networking. If you have your Azure Database instance behind a private network, you can't enable Azure SQL Database mirroring.

• Currently, you must update your Azure SQL logical server firewall rules to Allow public network access.
• You must enable the Allow Azure services option to connect to your Azure SQL Database logical server.

Active transactions, workloads, and replicator engine behaviors

• Active transactions continue to hold the transaction log truncation until the transaction commits and the mirrored Azure SQL Database catches up, or the transaction aborts. Long-running transactions might result in the transaction log filling up more than usual. The source database transaction log should be monitored so that the transaction log does not fill. For more information, see Transaction log grows due to long-running transactions and CDC.
• Each user workload varies. During initial snapshot, there might be more resource usage on the source database, for both CPU and IOPS (input/output operations per second, to read the pages). Table updates/delete operations can lead to increased log generation. Learn more on how to monitor resources for your Azure SQL Database.

Tier and purchasing model support

The source Azure SQL Database can be either a single database or a database in an elastic pool.

• All service tiers in the vCore purchasing model are supported.
• For the DTU (Database Transaction Unit) purchasing model, databases created in the Free, Basic, or Standard service tiers with fewer than 100 DTUs are not supported.

Next step

Tutorial: Configure Microsoft Fabric mirrored databases from Azure SQL Database

Related content

• How to: Secure data Microsoft Fabric mirrored databases from Azure SQL Database
• Limitations in Microsoft Fabric mirrored databases from Azure SQL Database
• Monitor Fabric mirrored database replication
• Troubleshoot Fabric mirrored databases from Azure SQL Database