Database Journal
MS SQL Oracle DB2 Access MySQL PostgreSQL Sybase PHP SQL Etc SQL Scripts & Samples Links Database Forum

» Database Journal Home
» Database Articles
» Database Tutorials
MS SQL
Oracle
DB2
MS Access
MySQL
» RESOURCES
Database Tools
SQL Scripts & Samples
Links
» Database Forum
» Sitemap
Free Newsletters:
DatabaseDaily  
News Via RSS Feed


follow us on Twitter
Database Journal |DBA Support |SQLCourse |SQLCourse2
 

Featured Database Articles

MS SQL

Posted Oct 8, 2008

Setting up a Two-NODE SQL Server 2008 Cluster from the Command Prompt - Integrated Installation

By Yan Pan

In Part 1 of this series, we discussed how to prepare for SQL Server cluster installation on a two-node Windows Server 2003 cluster. We had two machines, NODE1 and NODE2, in our example. In this installment, I will show you how to install SQL Server Database Engine on the cluster. Although Analysis Services can be clustered as well, and even put in the same resource group, it is recommended to install it in a separate group so SQL Server and Analysis Services do not affect each other in the event of a problem. Therefore, we will only install SQL Server Database Engine in the example below. This article series is written based on the SQL Server 2008 RTM Developer Edition.

In the Integrated installation, we create a single-node SQL Server failover cluster instance first. Then we run Setup on each node we want to add to the cluster, and add the node using the Add Node functionality in Setup. These two steps are shown in detail below.

1.  Install a single-node SQL Server failover cluster instance on NODE1.

Our SQL Server installation media is in a shared folder called sqlserver2008 on a remote computer demopc. We run the following command in the command prompt (please replace xxxxxxxxx with your own password before you run the command in your environment).

\\demopc\sqlserver2008\setup.exe /q 
 /ACTION=InstallFailoverCluster 
 /FEATURES=SQL 
 /INSTANCENAME="MSSQLSERVER" 
 /INSTANCEDIR="C:\Program Files\Microsoft SQL Server" 
 /INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server" 
 /SQLSVCACCOUNT="PowerDomain\SqlService" 
 /SQLSVCPASSWORD="xxxxxxxxx" 
 /AGTSVCACCOUNT="PowerDomain\SqlService" 
 /AGTSVCPASSWORD="xxxxxxxxx" 
 /SQLDOMAINGROUP="PowerDomain\SQLAdmins" 
 /AGTDOMAINGROUP="PowerDomain\SQLAdmins" 
 /SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS" 
 /FAILOVERCLUSTERGROUP="SQL Server 2008 Group" 
 /FAILOVERCLUSTERDISKS="SQL Data" "SQL Log" 
 /FAILOVERCLUSTERIPADDRESSES="IPv4;192.168.1.12;Public;255.255.255.0" 
 /FAILOVERCLUSTERNETWORKNAME="SQL2008Cluster" 
 /SQLSYSADMINACCOUNTS="PowerDomain\SqlService" 
 /SQLUSERDBLOGDIR="L:\MSSQL10.MSSQLSERVER\MSSQL\Log" 
 /SQLTEMPDBLOGDIR="L:\MSSQL10.MSSQLSERVER\MSSQL\Log" 
 /INSTALLSQLDATADIR="D:\MSSQL10.MSSQLSERVER\MSSQLSERVER"

Download this code.

Figure 1 shows the output from the command. The passwords are masked in the figure.

output from installing a single-node SQL Server failover cluster instance on NODE1
Figure 1

As you can see in Figure 1, a few parameters are passed to setup.exe to configure the new failover cluster instance. Each parameter is explained in the table below.

Parameter

Description

/ACTION=InstallFailoverCluster

Specifies that a single-node SQL Server failover cluster instance will be installed.

/FEATURES=SQL

Specifies that only SQL Server Database Engine will be installed.

/INSTANCENAME="MSSQLSERVER"

Specifies a default instance will be installed.

/INSTANCEDIR="C:\Program Files\Microsoft SQL Server"

Specifies that the SQL Server binaries will be placed under the directory C:\Program Files\Microsoft SQL Server.

/INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"

Specifies that the shared components will be placed under the directory C:\Program Files\Microsoft SQL Server.

/SQLSVCACCOUNT="PowerDomain\SqlService"

Specifies the SQL Server service account.

/SQLSVCPASSWORD="xxxxxxxxx"

Specifies the password for the SQL Server service account.

/AGTSVCACCOUNT="PowerDomain\SqlService"

Specifies the SQL Server Agent service account.

/AGTSVCPASSWORD="xxxxxxxxxx"

Specifies the password for the SQL Server Agent service account.

/SQLDOMAINGROUP="PowerDomain\SQLAdmins"

Specifies the domain group that contains the SQL Server service account, and will be used to control access to registry keys, files, SQL Server objects, and other cluster resources.

/AGTDOMAINGROUP="PowerDomain\SQLAdmins"

Specifies the domain group that contains the SQL Server Agent service account.

/SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"

Specifies the collation setting for the SQL Server failover cluster instance.

/FAILOVERCLUSTERGROUP="SQL Server 2008 Group"

Specifies the cluster group that will contain the SQL Server resources.

/FAILOVERCLUSTERDISKS="SQL Data" "SQL Log"

Specifies the shared disks that will be used to store SQL Server data. In our example, “SQL Data” is the resource name for the shared disk D:, and “SQL Log” is the resource name for the shared disk L:.

/FAILOVERCLUSTERIPADDRESSES="IPv4;192.168.1.12;

Public;255.255.255.0"

Specifies the network IP address for the new failover instance is 192.168.1.12 on the Public network.

/FAILOVERCLUSTERNETWORKNAME="SQL2008Cluster"

Specifies the network name for the SQL Server cluster.

/SQLSYSADMINACCOUNTS="PowerDomain\SqlService"

Specifies the logins that will be provisioned with the sysadmin permissions.

/INSTALLSQLDATADIR="D:\MSSQL10.MSSQLSERVER\

MSSQLSERVER"

Specifies all the SQL Server data files will be placed under the directory D:\MSSQL10.MSSQLSERVER\MSSQLSERVER on the shared disk D:.

/SQLUSERDBLOGDIR="L:\MSSQL10.MSSQLSERVER\MSSQL\Log"

Specifies the log files of all user databases will be placed under the directory L:\MSSQL10.MSSQLSERVER\MSSQL\Log on the shared disk L:.

/SQLTEMPDBLOGDIR="L:\MSSQL10.MSSQLSERVER\MSSQL\Log"

Specifies the log files of the tempdb database will be placed under the directory L:\MSSQL10.MSSQLSERVER\MSSQL\Log on the shared disk L:.

Tip:

If you encounter a “broken fusion ATL” error during rule checks, you can install the SQL Server Setup support files from the installation media before Setup. To do so, manually execute SqlSupport.msi under the setup folder in the installation media. For more information, please refer to http://support.microsoft.com/kb/955792.

After the installation, we need to check the log files under the SQL Server program directory. Figure 2 shows the list of log files.

the list of log files
Figure 2

The summary file, in our case, Summary_NODE1_20080824_221906.txt provides the final results of each component installation.

If the installation succeeded, the SQL Server cluster group should look as in Figure 3. Please note that only NODE1 is included in the cluster so far.


border=0 width=614 height=430 id=
Figure 3

2.  Add NODE2 to the cluster using the Add NODE functionality in Setup. Run the following command in the command prompt.

\\demopc\sqlserver2008\setup.exe /q 
 
 /ACTION=AddNode 
 /INSTANCENAME="MSSQLSERVER" 
 /SQLSVCACCOUNT="PowerDomain\SqlService" 
 /SQLSVCPASSWORD="xxxxxxxxx" 
 /AGTSVCACCOUNT="PowerDomain\SqlService" 
 /AGTSVCPASSWORD="xxxxxxxxxx"

Download this code.

Notice that the value for the ACTION parameter is AddNode, which specifies adding a new node into the cluster. Figure 4 shows the output from the command. The passwords are masked in the figure.

output of Add NODE functionality command
Figure 4

After the installation, we need to verify the result of the installation by checking the log files under C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log. If the installation was successful, we can perform a failover test to ensure automatic failover in case of a hardware or software failure. As shown in Figure 5, right click the SQL Server 2008 Group in Cluster Administrator, and choose Move Group.

Integrated-Verify.JPG
Figure 5

The SQL Server cluster group should fail over to NODE2, and the new SQL Server failover cluster instance should start running on NODE2. Figure 6 shows the SQL Server cluster after the failover.

Integrated-Verify2.JPG
Figure 6

Conclusion

In Part 2 of this series, we have illustrated how to install a SQL Server 2008 cluster using the Integrated Installation option. In the next installment, we will explore the Advanced Installation option.

» See All Articles by Columnist Yan Pan



MS SQL Archives

Comment and Contribute

 


(Maximum characters: 1200). You have characters left.

 

 




Latest Forum Threads
MS SQL Forum
Topic By Replies Updated
SQL 2005: SSIS: Error using SQL Server credentials poverty 3 August 17th, 07:43 AM
Need help changing table contents nkawtg 1 August 17th, 03:02 AM
SQL Server Memory confifuration bhosalenarayan 2 August 14th, 05:33 AM
SQL Server Primary Key and a Unique Key katty.jonh 2 July 25th, 10:36 AM