IT Depends

a database administration blog


March 2015

Microsoft Windows Server and annoying out of the box settings

This will be a short rant.

Why, oh why, when your operating system relies so heavily on file extensions to operate do you hide extensions to known file types by default?  Why Microsoft?  Why?



Installing a SQL Server failover cluster and configuring and migrating databases (Part 2)

So, you have a Windows 2012 R2 Cluster, you have your copy of SQL Server 2008 R2 all slipstreamed with SP2 or above, you’re good to go, you launch the installer and at the cluster verification check you get a “Cluster Service verification rule” failure.  This issue was detailed by Microsoft in their document titled “How to use SQL Server in Windows 8, Windows 8.1, Windows Server 2012 and Windows Server 2012 R2” but since this will very likely be a common complaint, I’ll list it in more detail here.

This is the error message you will be presented with:


The reason you’re getting this is due to MSClust.dll not being enabled.  This is a COM-based library that forms the Failover Cluster Automation Server feature that you can easily install with the following PowerShell Cmdlet:

 add-windowsfeature RSAT-Clustering-AutomationServer

You’ll need to run an elevated PowerShell for this command.  Since this is a Remote Server Administration Tool, I have no idea what would happen if you were running a Windows Server 2012 R2 Core installation.  Maybe this is why Microsoft recommend you don’t install Core for SQL Server.


Installing a SQL Server failover cluster and configuring and migrating databases (Part1)

Today I installed SQL Server 2008 R2 Standard on a Windows Server 2012 R2 cluster.  Not my preferred choice of SQL Server product but needs must.

With the hardware built, the Windows cluster built and the whole set up ready and waiting for a purpose, I went ahead and installed SQL Server.

My excitement was short lived as I had failed to read a very useful article from Microsoft (possibly the only one I hadn’t read), outlining in perfect detail, the issues with versions of SQL Server that don’t play so well with Windows Server 2012 R2.  For your convenience, that article is here:

It turns out that SQL Server 2008 R2 won’t play nice with Windows Server 2012 R2 unless it is patched up to SP2 or above.  This lead me to another article I hadn’t read on how to slipstream a service pack into the installer.  Something I’d never done before but had heard Hardware support guys bash on about when sliding SP3 for XP in.  Again for your convenience, see that article here:

Despite what the article claims, if you’re very sure which architecture you’re going to use, you will only need to slipstream the relevant one.  I patched up to SP3 and was then allowed to continue onwards with my install.


The beginning

Hi there.  Welcome to IT Depends, a database administration blog.

Here’s the obligatory first blog post to get us started and as a special treat, I’ll let you in on what to expect post wise.

Initially there won’t be many posts but my aim is to document any challenges or interesting developments in my day to day activities as a Production DBA.  Some posts may simply document something I have read, others will offer solutions to complex issues I have faced or problems I have had to fix.

So stick around, check back every now and then and please contribute to this as you see fit.


Blog at

Up ↑