SQL Server clustering is a powerful feature that allows for high availability and failover support in SQL Server installations. In this article, we will address some common questions and concepts related to SQL Server clustering.

Question 1: Creating a New Instance

One of the common questions when setting up a SQL Server cluster is how to create a new instance. Let’s say we have two nodes, SQLNODE1 and SQLNODE2, and we want to create a new instance for our SharePoint installation. The question is whether the new instance will be named SQLSERVER\SHAREPOINT or if the server name will be new as well.

The answer is that we need to use a new SQL Server network name for the new instance. The new SQL Server clustered instance would have a new server name, such as “new_name\SHAREPOINT”. To install the new SQL Server cluster instance, we need to launch the SQL Server setup file and select “New SQL Server Failover Cluster installation”. Then, follow the wizard and choose the features you want to install. On the Instance Configuration page, specify a new SQL Server Network Name, such as “Sharepoint”.

Question 2: Server Name in SQL Clustering

Another question that often arises is whether the server name changes when creating a new instance in SQL clustering. In standalone SQL servers, the server name does not change when a new instance is created. However, SQL clustering is different in this regard.

In SQL clustering, we need to specify the SQL Server Network name. The client should connect to the SQL Server using the SQL Server Network Name. If it is a default SQL Server instance (named MSSQLSERVER), we should connect using the SQL Server Network Name. If it is a named instance, we should connect using the naming format “SQL_Virtual_name\Instance_name”.

Question 3: Disk Failover in SQL Clustering

When setting up a new failover SQL cluster, it is common to move all the SQL resources to one node before installation. However, this can cause issues when it comes to disk failover. For example, if drives E and F failover to node B, it may be impossible to install database files on drive E and log files on drive F from node A.

The solution to this problem is to use different cluster drives for the new SQL Server cluster instance. The cluster drives E and F that are used by the existing SQL Server cluster cannot be shared with another SQL Server cluster.

These are just a few examples of common questions related to SQL Server clustering. By understanding these concepts, you can ensure a smooth installation and configuration process for your SQL Server clusters.