Forum Discussion
Mirroring for SQL Server 2025 installed on Azure VM
hi, we have got SQL server 2025 installed on a Azure VM. (recently updated from 2016 to 2025 of our instances).
I need to bring this data into Onelake. what is the best possible option.
We prefer mirroring, but it doesnt look like it is supported on SQL server 2025 on Azure VMs. Any thoughts.
db mirroring is deprecated and not supported in sql 2025. For bringing data from SQL 2025 on Azure VM into OneLake, use ADF or fabric data pipelines with CDC/Change Tracking for near real time sync. If you need continuous replication, consider Transactional Replication or Azure Data Sync as supported alternatives.
To clear the confusion here, Fabric Mirroring is the name of a new feature and different from Database Mirroring that SQL Server used to have form SQL Server 2005 and is now deprecated.
Fabric Mirroring is used to mirror tables from source SQL Server (or Azure SQL Database, Managed Instance or Fabric SQL Database) to OneLake in Microsoft Fabric in near real-time in delta parquet format and can be used for analytics in Fabric. The support for using mirroring from SQL Server 2025 running on Azure Virtual Machines is currently not available. This is on our roadmap and coming soon. You can however mirror from other lower versions or from SQL Server 2025 outside Azure.
To summarize:
1. Mirroring from SQL Server 2016-2022 is supported from Azure VM or outside Azure hosted environments.
2. Mirroring from SQL Server 2025 is currently supported from outside Azure hosted environments.
7 Replies
db mirroring is deprecated and not supported in sql 2025. For bringing data from SQL 2025 on Azure VM into OneLake, use ADF or fabric data pipelines with CDC/Change Tracking for near real time sync. If you need continuous replication, consider Transactional Replication or Azure Data Sync as supported alternatives.
To clear the confusion here, Fabric Mirroring is the name of a new feature and different from Database Mirroring that SQL Server used to have form SQL Server 2005 and is now deprecated.
Fabric Mirroring is used to mirror tables from source SQL Server (or Azure SQL Database, Managed Instance or Fabric SQL Database) to OneLake in Microsoft Fabric in near real-time in delta parquet format and can be used for analytics in Fabric. The support for using mirroring from SQL Server 2025 running on Azure Virtual Machines is currently not available. This is on our roadmap and coming soon. You can however mirror from other lower versions or from SQL Server 2025 outside Azure.
To summarize:
1. Mirroring from SQL Server 2016-2022 is supported from Azure VM or outside Azure hosted environments.
2. Mirroring from SQL Server 2025 is currently supported from outside Azure hosted environments.
Glad to hear this is on the roadmap. Is there any word on timeline?
Hi sgol ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you Vinodh247 for the prompt response.
I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.
Thank you.
hi, it looks like there is a confusion. i am talking about mirrored database in Fabric and its support for SQL 2025 deployed within Azure VM. I see this as one of the limitations in Fabric at the platform level. I am just curious if anything is in works, or why this limitation. https://learn.microsoft.com/en-us/fabric/mirroring/sql-server-limitations
sgol It does seem like there is a bit of controversy in this topic. If you look at the Fabric Roadmap here Microsoft Fabric Roadmap you'll see that Mirroring for SQL Server 2025 was shipped and is in the public preview:
But in the documentation here Limitations of Fabric Mirrored Databases From SQL Server - Microsoft Fabric | Microsoft Learn it clearly states that Mirroring for SQL Server 2025 on Azure VM is not supported:
I suppose you need to experiement and see what is working.
On the other hand, the answer that Vinodh247 provided is not suported by a reference to a corresponding documentation, which would be very useful if it explained what is going on here:v-venuppu I would vouch for more detailed answer on this topic with a link to some kind of documentation.
