Implementing a SQL Server HA/DR solution does not stop after production go-live. Once the system is ready for users, your job switches to operational support. This is where care and feeding is needed to make sure that the databases are highly available and will not be offline for an extended period of time.

This goes beyond installing patches, performing scheduled maintenance, and making configuration changes.

What if something unexpected happens? Something horribly goes wrong? How do you respond? Do you have history in your ticketing system where this has happened before? How do you deal with it?

It’s not enough that you know Always On Availability Groups. Or failover clustering. Or log shipping. Or backups. Or dealing with data corruption.

When dealing with an unexpected emergency, I noticed that most tech professionals do not have these 3 things. Maybe they have one or two but not all 3. To properly support a HA/DR solution, you need all these.

On this week’s episode of the Practical SQL Server HA/DR Show, I talk about the 3 things you need to properly support a HA/DR solution.

I’ll be doing this on a weekly basis so make sure you keep an eye out for announcements on my social media profiles (LinkedIn | Twitter | YouTube)