DBAs and systems administrators – oh, and even developers who were “volun-told” – responsible for managing SQL Server FCIs and AGs.
SQL Server Failover Clustered Instances (FCI) and Availability Groups (AG) depend a lot on Windows Server Failover Clustering (WSFC). But when mission-critical databases go offline, bringing them back online could be a nerve-wracking experience.
This session will look at understanding how the underlying WSFC platform works to help us maintain availability of our databases. This is for DBAs and systems administrators who are responsible for administering SQL Server FCIs and AGs but are not so comfortable with figuring out why the databases went offline and what they can do about it. We’ll walk thru the troubleshooting process that I follow to quickly identify and resolve SQL Server FCI and AG availability issues.
Why I Want to Present This Session:
Far too often, I see DBAs and system administrators scrambling to figure out what caused a SQL Server Failover Clustered Instance (FCI) or Availability Group (AG) to go offline and how they can quickly bring it back online without violating service level agreements. This session highlights the simplified process of identifying and quickly resolving availability issues with SQL Server FCIs or AGs.