Most IT Professionals – DBAs and sysadmins alike – spend a lot of time on the technical details of an HA/DR implementation. They learn as much as they can about a specific feature, the best practices approach to deployment, and the caveats specific to their use case. And every time an outage occurs, the focus keeps coming back to the tech.

– Did the configuration change recently?

– Was there a missing cumulative update?

– Should we increase the threshold values?

– Was the server reboot that caused the issue?

While an HA/DR solution is technical in nature, focusing on the tech is the main reason why outages and other related problems keep happening. And unless you step up as the trusted technical advisor in your organization, you’re going to get all the blame when an outage occurs.

On this week’s episode of the Practical SQL Server HA/DR Show, I talk about the reasons why focusing on tech is the worst way to deploy a HA/DR solution. I’ll also talk about a framework that I use every time I deploy a HA/DR solution that guarantees covering all bases.

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)