locked
SQL 2008 vs. SQL 2012 RRS feed

  • Question

  • Good Afternoon, 

    We are in the process of migrating our databases that are currently SQL 2005 and SQL 2008 to new servers. 
    Server OS is Windows 2012 R2 w/ SQL 2012 installed.
    SQL Servers are virtual built on ESX 6.0 hosts. Microsoft Clustering is being used along with the SQL Always On technology.
    Our DBAs have been able to get SQL 2012 installed, setup the resources in the cluster and not have issues. 

    One of the applications they are migrating is only certified on SQL 2008.  The servers were built and Failover Clustering was installed.   The cluster was created and has the core resources..cluster name, cluster IP and FSW for the Quorum. 
    SQL 2008 was installed on the first node of this cluster without issue.  When the DBAs attempt to install it  on the second node they are receiving errors during the rule checks. 

    First error was resolved by using the Install-WindowsFeature RSAT-Cluster-ServerAutomation Command.  Ran through the install again and it is failing the rule check looking for a cluster disk.  Normally, when SQL 2012 is installed and using Always On, we do not have to add the disks into cluster since they will not be failing over between nodes. 

    Is there some difference between how a cluster installation is performed for SQL 2008 vs. SQL 2012?
    Are AlwaysOn availability groups an option in SQL 2008?  And if so, how do we get past this rule check?  Did see where you can run the setup.exe with a switch to skip rules checks, but can't imagine that is a best practice.
    Since it is a SQL 2008 cluster, does there need to be at least one shared disk in the cluster? This presents the problem because the nodes of the clusters are in out data centers. The disks are vmdk files. 

    Any insights would be greatly appreciated.  Up to this point all the clusters using the Always On Technology have been Windows 2012 R2\ w SQL 2012 installed. This is the first AO cluster that is using SQL 2008. 

    Thank You


    Wednesday, September 7, 2016 6:06 PM

Answers

  •  Normally, when SQL 2012 is installed and using Always On, we do not have to add the disks into cluster since they will not be failing over between nodes. 

    Is there some difference between how a cluster installation is performed for SQL 2008 vs. SQL 2012?

    Hi,

    There is lot of difference and you can see into features supported by various editions of sql server. I mean SS 2012 is way ahead in terms of clustering as compared to 2008. But your case is the windows cluster requirement for AlwaysON is different from Normal cluster. You dont necessarily need shared storage in AlwaysON cluster, you can build windows node with just fileshare witness and no shared storage while in SQL Server 2008 cluster you have to have a shared storage .


    Are AlwaysOn availability groups an option in SQL 2008?

     And if so, how do we get past this rule check?  Did see where you can run the setup.exe with a switch to skip rules checks, but can't imagine that is a best practice.
    Since it is a SQL 2008 cluster, does there need to be at least one shared disk in the cluster? This presents the problem because the nodes of the clusters are in out data centers. The disks are vmdk files.

    
    

    No you CANNOT have AlwaysON Availability groups in SS 2008 this feature was introduced in SS 2012.

    For second part answer is simple you have to have shared storage assigned to the windows cluster without that you cannot proceed. Get in touch with storage team. Skipping rule was option when some rule check was not applicable to you and was unnecessarily causing hindrance, definitely not your scenario



    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    Wednesday, September 7, 2016 6:22 PM