Table of Contents
Note: If you buy something from our links, we might earn a commission. See our disclosure statement.
With the release of SQL Server Always on Availability groups in 2012 Enterprise Edition, it became the De facto standard for High Availability and Disaster Recover Solutions. The reason why it was so successful was because of the flexibility that the solution provides. Scale-out reads, DR integration to an Azure VM, backups on secondary etc. As much as it is successful, its main limitation was its Enterprise Edition only feature restriction. Most SQL Standard deployments still relied on the older methods like Database Mirroring, Log shipping, 2 Node Clustering etc. That is something that has changed with SQL Server 2016. SQL 2016 introduces the basic availability groups. In this post, I am going to talk about what are SQL Server 2016 basic availability groups restrictions.
Database mirroring is planned to be deprecated in its future releases. For any new production deployment planning, basic availability groups need to be considered over Database mirroring for its benefits.
Here is the Microsoft Official documentation for your reading pleasure.
Comments are closed.