SQL Server in Windows Server Environment

This blog is intended to be a guideline for installing SQL Server in Windows Server environments. This came about as I am heavily involved with virtualizing SQL Server in different Windows environments. Detailed information can be found in kb2681562

I will touch base on the following Windows environments:

  1. Windows Server 2012R2
  2. Windows Server 2012

SQL Server 2005

Note that SQL Server 2005 (including SPs) and all earlier versions of SQL Server are  not supported on Windows 2012 / R2. An upgrade will be required before housing your SQL environment on Windows 2012 / R2. (If you need help in uninstalling SQL 2005 you can follow kb909967)

Minimum requirements for SQL Server on Windows 2012R2

  • SQL Server 2008 – You need to apply SP3 or later. Per MSFT RTM installation of the product is supported but installation of service pack (SP3) after the initial installation is must.
  • SQL Server 2008R2 – You need to apply SP2 or later. Refer to Known Setup Issues
  • SQL Server 2012 – You need to apply SP1 or later. Refer to Known Setup Issues
  • SQL Server 2014 – You can install RTM or later.

Minimum requirements for SQL Server on Windows 2012

  • SQL Server 2008 – You need to apply SP3 or later
  • SQL Server 2008R2 – You need to apply SP1 or later.
  • SQL Server 2012 – You can install RTM or later.
  • SQL Server 2014 – You can install RTM or later.

Known SQL Server 2008/R2 Setup Issues

Issue#1 – Cluster Service Verification rule fails with SQL 2008R2 Cluster Instance

When installing a new SQL Server 2008R2 failover cluster instance we kept running into “Cluster Service verification” rule.

SQL2008R2_ClusterServiceVerification

SQL2008R2_ClusterFailure

Further researches lead me to 2 things which resolved the issue:

  • SlipStream installation of SQL2008R2 with SP3 (will blog about this soon)
  • An excellent article by Daveberm on how to enable the Failover Cluster Automation Server in the Add Roles and Features via wizard or powershell

Cause

This is caused by COM-based MSCls.dll library not being enabled.

Resolution

  • Run the following powershell on each of the nodes to enable the featur
add-windowfeature RSAT -Clustering-AutomationServer
  • Run the wizard on each node using Server Manager. Expand Remote Server Administration Tools → Feature Administration Tools → Failover Clustering Tools and click on Failover Cluster Automation Server

RolesandFeatures

 

In my case I was doing fresh installations (RTM) and needed slipstream in order to install it on Win 2012R2. My next blog will be all about Slipstream and its benefits.

Updates – here is my blog on Slipstreaming SQL Server

~ Adios

Khan

Like us on FaceBook | Join the fastest growing SQL Server group on FaceBook |

Follow me on Twitter

 

Data Platform Virtual Summit 2020

Subscribe to SQLServerGeeks YouTube channel. If you want more learning content in your inbox, subscribe to SQLServerGeeks Bulletin.

SQLServerGeeks YouTube | SQLServerGeeks Bulletin | SQLServerGeeks Twitter

Avatar

About Arsalan Khan

People know me as 'Khan' ... nope not Shah Rukh's movie but Star Trek II - Wrath of Khan and since than 'Khan' it has been. Born and raised in Dubai before moving to US for my masters. Been blessed with solid 8+ yrs with SQL (and counting) and currently working for the biggest publishing house as Sr. Database Administrator. I have had an opportunity to speak about tips & tricks to write efficient tsql for Quest International Users Group (PeopleSoft). Love playing TT, badminton and thoroughly enjoy watching cricket when not occupied with my loving daughter. Expertise in DR, Performance Tuning, Troubleshooting and Problem Solving. With that being said I have finally decided to roll my sleeves up and give back to the community bit by bit. Finally.. as my wonderful wife puts it ... "if you don't have a smile, I will give you one of mine ~ Rabia Khan" ~Cheers

View all posts by Arsalan Khan →

2 Comments on “SQL Server in Windows Server Environment”

Leave a Reply

Your email address will not be published. Required fields are marked *