At MS Ignite this week, several details were revealed about the changes in Availability Groups that will ship in SQL Server 2016. I wanted to provide a very quick list of bullets on the major highlights at a high level, to get you excited about these AG enhancements:
- Optional setting to fail over based on database failure – in 2012 and 2014, failover is determined almost entirely at the instance level. If a database goes offline, suspect, or corrupt, the AG keeps humming along. In SQL Server 2016, you will be able to have certain database metrics to initiate failover for the entire group.
- Distributed Transaction Coordinator support – in current versions, MSDTC is not supported for AG databases, but it will be fully supported in SQL Server 2016 (it will require an operating system update as well – it is possible that you will need the most recent version of Windows Server for full support across all scenarios).
- Group Managed Service Accounts are fully supported – these "worked" in SQL Server 2012/2014, but were not fully supported, and had some issues (see background information here, here, here, and here).
- Load Balancing for Readable Secondaries – you will be able to use a round-robin mechanism for routing read-only requests through the listener to take balanced advantage of all secondaries, versus the current approach of requests always going to the "first" available secondary.
- Additional synchronous failover targets – currently, only one synchronous automatic failover target is allowed. In the next version, you'll be able to specify up to three total secondaries for automatic failover.
- Improved log transport performance – this entire pipeline was overhauled and refactored for lower CPU usage and higher throughput.
- Basic Availability Group – this option appears in the AG wizard in CTP2. One could imagine that this is destined to be the mirroring replacement for Standard Edition, but we'll wait for further announcements to confirm.
The post SQL Server 2016 : Availability Group Enhancements appeared first on SQLPerformance.com.
