SQL Server – Installing SQL Server 2012 Cluster

Microsoft Cluster

A Microsoft cluster is a high-availability system designed to keep the database up as much as possible. It does this by resuming processing on the secondary server in the event of a failure on the principal server. Since the data resides on a shared disk, a Microsoft cluster will not survive a data corruption.  This technology is high availability, not disaster recovery. All data resides in the same data center and on the same disk. A cluster can be used with other technologies, such as database mirroring.





In order to Install SQL Server Cluster, we need to have Windows cluster ready as a base with some other pre-requisites as well. [ Installing Windows Cluster is out of scope of this article.]

1- Windows Cluster

2- DTC

3- SQL




We then need to setup 2 Network Interfaces to be used in production and the other as a heartbeat.

Once the setup is ready to install SQL Server Cluster. Please follow the below steps to configure 2 Node Active/Passive Cluster[SQL Server 2012].


Steps to be performed on Node 1.

1. With the SQL Server installation binaries available, right click “Setup” and run as administrator:





2.  Click “Installation” in the left menu, then select “New SQL Server Failover Cluster Installation”




3. A check will run in order to find possible constraints when installing the SQL Server Setup support files. At the end of the check, click “OK”




4. Provide product key for your media. Then Next



5. Accept License Agreement (and the other check if you would like). Then Next


6.  Wait for Setup Support Rules check. Once done make sure no failed task. Evaluate warnings for your environment . Then click Next




7. click SQL Server Feature Installation and click Next.



8. Select Features to install and click NEXT. I have selected all Features.


9. Make sure feature Rule check complete with no Failed status. Then Next





10. Provide Network and Instance names. Then Next





11. Click Next



12. Click Next




13. Select Disk needed for the resource group . Then Click Next



14.  Enable IP4 and provide IP address. Then Next




15. Provide Service Accounts (and Collation if different than default – SQL_Latin1_General_CP1_Cl_AS). Then Next

16 17

16. Now we need to choose the authentication mode of our instance.The options are either “Windows Authentication”, which will take benefit from domain and local server logins, or “Mixed Mode”, which accepts Domain/Windows logins as well as logins created and managed by SQL Server.If you pick “Mixed Mode” a login called “sa”, member of the “Sysadmin” role will be enabled. For this reason we need to specify the password for this login.In the box bellow, we need to add all domain/Windows users that have access to the instance and will be part of the “Sysadmin” fixed server role. You need to use the three buttons to add/remove logins from this list:



17. Select data directories accordingly for Datafile, log file, tempdb files and backup files and click next.



18. If you have selected analysis features then on this screen add the administrator account and data directory for analysis service. Then click next







19. Select install only for reporting services and Click Next. You can configure reporting services later.





20. Check the error report and click NEXT.




21. Make sure no clusters rules failed. Then Next



22. Click Install.


25 26



23. Click Close to complete the installation.





Check the Failover Cluster Manger. And you would see SQL Service and other dependent resources running under it.





Adding Node to cluster will be covered in next post.



 Hope this was helpful !!!


Installing SQL Server 2008 R2 Cluster





Applying service packs (Hotfixes) to SQL Server Cluster 2008R2

When an instance of SQL Server is configured for HA like Cluster, then it is important to install service packs (hot fixes) in proper sequence.

Installing Service Pack SQL Server 2008/R2 in failover cluster is very different than the SQL Server 2005 cluster failover.

With SQL Server 2005,  install service pack (or hotfix) on the active node and the Setup will launch simultaneously  “remote silence” on all passive nodes. All nodes in the cluster containing the SQL Server instance are updated in the same time.

With SQL Server 2008, to reduce the downtime, the method of deployment is changed.

Below is the sequence to apply Service Pack, Cumulative Update or Hotfix in SQL Server 2008/R2 Cluster (2 Node Active/Passive :

1.  Apply the hotfix on pasive node (Node 2)
2.  Reboot the passive node (Node 2)
3.  Failover SQL resources from Node 1 to Node 2. This will make Node 2 Active and Node 1 Passive.
4.  Apply the hotfix on now passive node (i.e Node 1)
5.  Reboot the passive node Node 1.


Below are the screenshots for reference:

Download the Service Pack 1 and run the .exe (Node 2– Passive Node)


Click Next to Proceed





Accept licence terms and click Next


Make sure the SQL instance which needs to the patched is selected and click Next


Click Next, once files in Use completes.



Click Update to upgrade Service pack.





Once finished, Click close.



This complete the step 1.  Now reboot the currently patched node and then failover SQL resources to Node 2 from Node 1.

Repeat the same process of applying patch, on Node 1 now.  Once finished, take reboot of Node1 and check the status.

This completes the task of applying Service pack on SQL Cluster 2008/R2.


Hope this was helpful.