1. ALWAYSON AVAILABILITY GROUPS Replicas, Listeners & Quorums, Oh My! Kevin Howell SQL Saturday #517 Philadelphia, June 2016

2. ALL ABOUT ME Kevin Howell 3 Kids Cubmaster & Wrestling Coach 15 Years Developer & DBA Joined Microsoft ® in March 2016 Email: kevin@sqlpsi.comkevin@sqlpsi.com Website: www.sqlpsi.comwww.sqlpsi.com & 1 Wife

3. AGENDA Basics WHY? Terminology Modes Requirements Versions Good Stuff Environment Setup Availability Group Setup Failover Demo Details, Details… 2016 Improvements Keys to Success Questions

4. WHY?

5. WHY AGs? High Availability: Minimize disruption of service via hardware solution Disaster Recovery: Ability to reestablish services after an unplanned hardware outage Shared Goal: Ensure Data Integrity is maintained

6. 2016 2014 Rolling Upgrades WHY? 2014 Active Primary Passive Secondary 2016 Fail Over Active Primary Passive Secondary Steps 1)Stop Synchronizing 2)Upgrade Secondary 3)Failover to Secondary 4)Upgrade Primary 5)Restart Synchronization 6)Failover to Initial Primary 7)Restart Synchronization

7. TERMINOLOGY Window Server Failover Cluster Group of independent servers that work together to maintain availability of services Windows Server Failover Cluster Availability Group Container for a set of databases that failover together Instance 1Instance 2 Availability Group Listener Primary Replica Secondary Replica Primary Replica Makes databases available for read/write connections and sends transaction logs to secondary replicas Secondary Replica Maintains a copy of availability databases. Serves as a failover target. Allows Read- Only access and Backups Listener Virtual name to direct incoming database traffic to the primary replica or read-only secondary

8. A STEP FURTHER… SQL 2016 supports 8 secondary replicas (up to 2 synchronous commit)

9. JUST ONE MORE STEP… Symmetrical Hardware, but not necessary

10. MORE TERMINOLOGY Quoroum – collector of votes among nodes within the Availability Group to determine if state is healthy. Majority of votes wins Witness (File Share or Disk) – needed in cases where there are an even number of nodes in Availability Group for tie-breaker

11. DEMO Quorum & Witness in Azure Lab Windows Server VM (Failover Cluster Manager)

13. AVAILABILITY GROUP MODES Asynchronous Commit Mode: Primary commits without waiting for secondary verification of a hardened log Only Manual failovers are available with Asychronous MINIMAL TRANSACTIONAL LATENCY, POSSIBLE LOSS OF DATA Synchronous Commit Mode: Prior to transaction commit, secondary must confirm the log has been hardened Both Manual & Automatic failovers are available with Synchronous COMMITTED TRANSACTIONS ARE FULLY PROTECTED, INCREASED TRANSACTAIONAL LATENCY

14. REQUIREMENTS Window Server 2012 (For SQL 2016) Windows Server 2008 (For SQL 2014 & 2012) SQL Server Licenses 2016 Enterprise (Full Availability Groups) 2016 Standard (Basic Availability Groups) 2014 Enterprise 2012 Enterprise Windows Server Failover Cluster

15. AVAILABILITY GROUP VERSIONS SQL 2016 Enterprise SQL 2016 Standard SQL 2014SQL 2012 Secondary Replicas8184 Synchronous Secondary Replicas2122 Automatic Failover Targets3N/A11 AD Domain RequiredNo Yes DTC SupportYes No Group Managed Service AccountYes No Direct Seeding of ReplicasYes No

16. NOW THE GOOD STUFF… DEMO Azure Marketplace – Availability Group Cluster Environment Setup Availability Group Setup/Deployment Availability Group Management SSMS

17. SQL 2016 IMPROVEMENTS Log Transport Performance Development focused on matching PCIE Class Storage Streamlined Pipeline for Data Transport to Replicas Load Balancing among Read-Only Secondaries Read traffic spread across secondaries Standard Edition Basic Availability Groups Replacement for Database Mirroring 2 node AG (Primary + 1 Secondary), 1 Database

18. SQL 2016 IMPROVEMENTS Domain Independent Availability Groups Cross Domain/No Domain Options (think consolidation) Database Level Failover Trigger (instead of Instance Level) DTC Support with Availability Groups 3 Failover Available Replicas Group Managed Service Accounts (gMSA) Direct Seeding of Replicas (no backup onto secondaries)

19. KEYS TO SUCCESS Plan out your topology & failover processes Ensure infrastructure can support bandwidth for log transport Determine your geo-replication sensitivity Explore hybrid solution (on-prem/cloud) Consider Read-only secondaries for your reporting purposes

20. QUESTIONS?

21. CONTACT INFORMATION Email: kevin@sqlpsi.comkevin@sqlpsi.com Website: www.sqlpsi.com/presentations.htmlwww.sqlpsi.com/presentations.html

22. RESOURCES http://www.tech-coffee.net/sql-server-2012-2014-alwayson-availability- group/ http://www.tech-coffee.net/sql-server-2012-2014-alwayson-availability- group/ https://www.brentozar.com/sql/sql-server-alwayson-availability-groups/ https://channel9.msdn.com/Events/DataDriven/SQLServer2016/Always-On- Availability-Groups-Enhancements https://channel9.msdn.com/Events/DataDriven/SQLServer2016/Always-On- Availability-Groups-Enhancements https://popbi.wordpress.com/2014/06/26/always-on-availability-groups-do-i- need-a-file-share-witness-or-no/ https://popbi.wordpress.com/2014/06/26/always-on-availability-groups-do-i- need-a-file-share-witness-or-no/ https://azure.microsoft.com/en-us/blog/sql-server-alwayson-cluster- template-updated-with-internal-listeners-and-optimized-performance/ https://azure.microsoft.com/en-us/blog/sql-server-alwayson-cluster- template-updated-with-internal-listeners-and-optimized-performance/