Evolution of the Data Platform: SQL Server 2016 Always On Availability Groups (AGs) Enhancements

Evolution of the Data Platform: SQL Server 2016 Always On Availability Groups (AGs) Enhancements

Brew a fresh pot of coffee and be ready for the 24 Hours of PASS: Evolution of the Data Platform. Yes, it’s that time of the year, and I’m thrilled to share that my session on SQL Server® 2016 Always On Availability Groups (AGs) Enhancements was one of the most highly rated by the Program Committee and earned the coveted third slot at the event!

@PASS24HoP is a 24-hour long global event sponsored by the preeminent SQL Server organization on the planet, the Professional Association for SQL Server (PASS). My session will take place on Wednesday, May 25th at 10 a.m. EDT / 7 a.m. PDT / 2:00 p.m. UTC, where I will review the spectrum of feature and performance enhancements introduced in SQL Server 2016 Always On Availability Groups.

Always On Availability Groups (AGs)

Always On Availability Groups is SQL Server’s preferred high availability/disaster recovery (HA/DR) feature. AGs were introduced in SQL Server 2012 and improved in SQL Server 2014. Yet in SQL Server 2016 a wide range of fantastic enhancements are delivered, including performance enhancements that require flash to leverage them. The SanDisk® Data Propulsion Lab (DPL) has been busy putting the new bits through their paces—with fantastic outcomes.

Our work shows enhancements of 5x – 10x, allowing over ½GB/s (4Gb/s) across the wire. These improvements expand solutions options for Tier 1 OLTP and Data Warehouse workloads, Tier 1 and Tier 2 consolidation, and more.

Always On Availability Groups: SQL Server 2016 Enhancements

Here’s a partial agenda of the new! improved! functionality and performance:

  • SQL Server Standard Edition support(!)
  • Domain independent AG support
  • Load-balanced readable secondaries
  • Direct seeding of new DB replicas
  • Enhanced Azure integration
  • And more—including “AlwaysOn” now re-named to “Always On” (yes, really)

Most exciting of all are the performance improvements:

  • Log transport
  • Log redo

These changes move the bottleneck from the SQL Server codebase, allowing improved CPU utilization and far higher transaction rates. And the benefits aren’t limited to performance: this real-time transport of transactions to secondary replica(s) renders the data immune to failure of the primary servers and therefore results in improved RPO.

Join Me at 24 Hours of PASS: Evolution of the Data Platform!

See all 24 fantastic round-the-clock sessions for yourself. Learn about my session, SQL Server 2016 Always On Availability Groups Enhancements, and register for the event here.

You can follow us on twitter: @SanDiskDataCtr, the event at @SQLPASS and @PASS24HoP and yours truly at @aspiringgeek.

jimmy_may_DPL


Jimmy May: Jimmy is a SQL Server Certified Master and is a SQL Server Technologist with a passion for “flipping the /faster bit”.

Related Posts

SQL Server OLTP Consolidation – How to Get the Right S2D Caching Tier
SQL Server OLTP Consolidation – How to Get the Right S2D Caching Tier

How can you maximize your SQL Server OLTP Consolidation? Peter Plamondon looks at what you need to know about the caching tier and working set size to make SQL Server OLTP Consolidation, using Storage Spaces Direct, a success.

SQL Server 2008 EOS – a Perfect Storm for HCI and S2D
SQL Server 2008 EOS – a Perfect Storm for HCI and S2D

If you're in IT, you’re facing a change in server architecture and deployment with hyperconverged infrastructure; a change in storage architecture with software-defined storage, and another wave of SQL Server migration and consolidation with the [...]