Mirroring for SQL Server in Microsoft Fabric (Generally Available)
In today’s AI driven world, analytics platforms are only as good as their data. With the ever-increasing amount of data being collected in various applications, databases, and data warehouses in an enterprise, managing and ingesting data into a central platform for purposes of analytics and AI is a cumbersome and costly process.
Databases and data warehouses use proprietary storage formats making the ability to create shortcuts to their data impossible. Data needs to be extracted, transformed, normalized, and made available in a central place for analytics. Even when this is implemented, data is not real-time making any insights stale pretty quicky resulting in users having to query the data in the source.
Mirroring provides a modern way of accessing and ingesting data continuously and seamlessly from any database or data warehouse into OneLake in Microsoft Fabric. This is all in near real-time thus giving users immediate access to changes in the source!
Mirroring for SQL Server in Fabric for all in-market versions of SQL Server from SQL Server 2016 to SQL Server 2022 is Generally Available.
Additionally, with SQL Server (Generally Available), we are also excited to announce that Mirroring for SQL Server 2025 in Fabric is Generally Available.
Capabilities
Mirroring in Fabric from any of your SQL Server sources ensures that your source transactional SQL Server database is always up to date and available in the Fabric OneLake, providing a solid foundation for reporting, advanced analytics, AI, and data science. There is no complex setup or ETL for Mirroring. You setup the mirror from Fabric Portal by providing the SQL Server and database connection details, provide selections on what needs mirrored into Fabric, either all data or user selected eligible mirrored tables. And, just like that mirroring is ready to go. Mirroring SQL Server database creates an initial snapshot in Fabric OneLake after which data is kept in sync in near-real time with every transaction when a new table is created/dropped, or data gets updated.
Mirroring for SQL Server (2016-2022) in Microsoft Fabric
Mirroring for SQL Server to Fabric from these SQL Server versions relies on the Change Data Capture (CDC) technology available in SQL Server. CDC captures an initial snapshot of all the tables selected for mirroring and there after replicate the changes. Additionally, on-premises data gateway (OPDG) or VNet data gateway is required to be installed in your SQL Server environment. The mirroring services connects to OPDG to read the initial snapshot as well as the changes and pulls the data into OneLake and converts into an analytics-ready format in Fabric.
For detailed steps (including pre-requisites) to configure, and monitor mirroring from SQL Server to Fabric, refer to the Mirrored SQL Server documentation.
SQL Server 2022 mirroring setup and replication in action:
Mirroring for SQL Server 2025 in Fabric
While the main functionality and experience stays the same as above, mirroring from SQL Server 2025 uses change feed instead of Change Data Capture. This is the same technology used in mirroring for Azure SQL in Fabric. In this version, SQL Server keeps track and replicates the initial snapshot and changes to the landing zone in OneLake which is then converted to an analytics-ready format by the mirroring engine in Fabric. On-premises data gateway or VNet data gateway is primarily used as a control plane to connect and authenticate your on-premises environment to Fabric. Arc Agent is required for outbound authentication from SQL Server to Fabric.
Since the preview announcement, we have heard from many customers analyzing their data with Mirroring Azure SQL data, finding new insights and providing feedback.
With Fabric Mirroring in SQL Server 2025, ExponentHR can effortlessly mirror numerous datasets to fabric, enabling near real-time analytics. This technology has alleviated the need for expensive and complex ETL operations and enables more productivity for our customers. Thanks to SQL Server 2025’s built-in cloud connectivity, we can directly process large amounts of data efficiently and overcome traditional bottlenecks.
— Brent Carlson, IT Manager, ExponentHR
SQL Server 2025 mirroring setup and replication in action:
For detailed steps (including pre-requisites) to configure, monitor and troubleshooting mirroring from SQL Server 2025 data to Fabric, refer to the Mirrored SQL Server documentation.
The table below summarizes the differences between various SQL sources when mirroring to Fabric.
| SQL Server 2016-2022 | SQL Server 2025 | Azure SQL | |
| Capture incremental changes | Use “Change Data Capture (CDC)” | Use “Change Feed” method | Use “Change Feed” method |
| Uses Arc Agent | Not required | Arc Agent provide System managed identity for outbound authentication | Uses System managed identity auto created for Azure SQL |
| SQL Server Agent | CDC relies on SQL Server Agent for key functions of change captures | Not required | Not required |
| On-premises data gateway (OPDG) or VNet data gateway | OPDG or VNet data gateway writes data into OneLake | OPDG or VNet data gateway is used for control and command. SQL Server directly writes to OneLake | OPDG or VNet data gateway is required only when Azure SQL is configured in private network |
From here on, the mirrored data in the delta format is ready for immediate consumption across all Fabric experiences and features like Power BI with new Direct Lake mode, Data Warehouse, Data Engineering, Lakehouse, KQL Database, Notebooks and copilots work instantly.
Resources
Download the SQL Server 2025 bits today.
Learn more about what’s new with SQL Server 2025.
Try out Mirroring in Fabric, sign up for a free trial and get started.
