Every SQL Server high availability solution fall into these two (2) categories – ones that you built and ones that others built. Simple, right?

The problem lies when somebody else – a different team, a consultant, a managed services provider – built the solution, didn’t follow design and implementation best practices, and left the care and feeding to YOU. You struggle with addressing issues that should have been avoided if only the implementation was done properly. And you think the instructions that they left for you was good enough. All it did was create more confusion and introduced more issues.

Even worse is when it was you who designed the solution but were not aware of the proper design and deployment strategies needed for a stable and reliable environment.

In this episode of the Practical SQL Server HA/DR Show, I talk about how to deal with a crappy environment – whether it was you who built it or somebody else. I also talk about making sure that your SQL Server high availability environment is rock-solid, stable and reliable so you don’t have to struggle with unexpected outages and a lot of sleepless nights.

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)