Allan Hirt

Availability is a core tenet for any application using SQL Server 2025 or Azure SQL. You'll not only learn what's new in SQL Server 2025 and Azure SQL to see how you can meet your availability objectives and keep the business going, but also real world tips, tricks, dos, and don'ts for successful availability configurations on premises, hybrid, or in the cloud to be an availability hero back home.

There are very few who live on the bleeding edge or stay 100% up-to-date. That means the majority of technology deployments in the world – physical, virtual, or in the cloud – are behind.

There are very few who live on the bleeding edge or stay 100% up-to-date. That means the majority of technology deployments in the world – physical, virtual, or in the cloud – are behind.

There are three main ways to deploy Always On Availability Groups (AGs) and Always On Failover Cluster Instances (FCIs) - physical hardware, virtualized, and IaaS in the public cloud. Those are just three of the factors that influence how AGs and FCIs are planned, deployed, and adminstered.

There are three main ways to deploy Always On Availability Groups (AGs) and Always On Failover Cluster Instances (FCIs) - physical hardware, virtualized, and IaaS in the public cloud. Starting with SQL Server 2017, we now also have the ability to use Windows Server or Linux.

Always On Availability Groups (AGs) have evolved since their introduction in SQL Server 2012. Not only is there the “classic” form of AGs, but now there are Basic Availability Groups, Distributed Availability Groups, Domain Independent Availability Groups, and Read Scale Groups.

Whether you are deploying on premises (physical or virtual) or up in a public cloud (Amazon Web Services, Microsoft Azure, or Google Cloud Platform), your SQL Server databases and instances need to be highly available.

Since we live in a world where physical deployments are more the exception than the rule, the infrastructure underneath our databases is similar, yet very different. There is still CPU, disk, and memory but what does that actually mean today?

Since we live in a world where physical deployments are more the exception than the rule, the infrastructure underneath our databases is similar, yet very different. There is still CPU, disk, and memory but what does that actually mean today?

There are three main ways to deploy Always On Availability Groups (AGs) and Always On Failover Cluster Instances (FCIs) - physical hardware, virtualized, and IaaS in the public cloud. Starting with SQL Server 2017, we now also have the ability to use Windows Server or Linux.