So… this is it how it happened… the previous database administrator had setup SQL Server 2008 mirroring within the same domain using encrypted traffic and certificated endpoints. Why? I hear you cry. Well, I maybe a complete database zealot – but I understand the KISS principle (I’m not a cop out – oh so cynical reader). So when the certificates expired, and the mirrored database [high safety - synchronous] quietly died like a flan in a cupboard (thanks Eddie Izzard)… I had to put the thing back together. Being a little rusty in setting up the mirror, I headed to Google for all my answers and stumbled upon the usual gold mine – Microsoft Books Online… where a beautiful how-to professed to fix all aliments (lie #1) and allow any Tom, Dick or Database Zealot to setup super cool mirroring (lie #2). Oh dear reader, how much it lied with it’s accurately described processes and instructions – which turned out to be missing rather large pieces of instruction (or maybe I couldn’t read properly… but let’s not let the facts stand in the way of a jolly good post now).
So… What did I discover. I discovered that a) The Database Mirroring Wizard does all the work that the document tells you to setup manually (and incorrectly) and b) NEVER set your administration account’s default database to anything other than master.
Yep. I did that. What a FAIL.
Well come on it was Tuesday and I was already suffering after my household of four kids, a stomach bug and the traffic snarl in the morning had taken most of my brain power by 8am. That, and I even think the wind was blowing from the South.
Besides the impending odds, I eventually got the process happening by following these simple steps (on a SQL Server 2008 Enterprise install): Continue reading