Name: Why Most Always On Availability Groups Implementations Fail
Start: 2026-09-15T13:00:00-05:00
End: 2026-09-15T14:30:00-05:00

A SQL Server Always On Availability Groups deployment can be technically correct and still fail to deliver the expected business outcome. And this becomes more obvious when different teams who need to take care of the infrastructure are not involved in the planning and implementation.

This session covers why most Always On Availability Groups implementations fail and challenges the way many organizations approach HA/DR projects. It will also cover how to guarantee implementation success.

David Klee

Microsoft Data Platform Continuity Virtual Group

Azure Data Tech Groups

Technology

Open Source

Database Professionals

Software Development

SQL Server

Database Development

Microsoft Azure

Advanced SQL Server

**Edwin M Sarmiento** is the Managing Director of 15C, a consulting and training company that specializes in designing, implementing and supporting SQL Server infrastructures. He is a former Microsoft Data Platform MVP for 12 years and Microsoft Certified Master from Ottawa, Canada (but he’s originally from the Philippines) specializing in high availability, disaster recovery and system infrastructures running on the Microsoft server technology stack. His background in Unix has taken him to the world of DevOps and Docker to containerize SQL Server. He is very passionate about technology but has interests in music, professional and organizational development, leadership and management matters when not working with databases.

Outside of work you can find him playing jazz music on his keyboard or guitar, going on nature hikes, doing wilderness camping, running races, and training to become a pilot.

Microsoft Data Platform Continuity Virtual Group

Why Most Always On Availability Groups Implementations Fail

Microsoft Data Platform Continuity Virtual Group

Details

Related topics

You may also like