Article ID: 930057 - Last Review: November 30, 2007 - Revision: 1.1

How to upgrade to a full version of SQL Server for use with Windows Compute Cluster Server 2003

View products that this article applies to.

On This Page

Expand all | Collapse all

SUMMARY

Windows Compute Cluster Server 2003 (Windows CCS 2003) is a High Performance Computing (HPC) solution from Microsoft. Windows CCS 2003 includes the Compute Cluster Pack component. This component provides the interfaces, the tools, and the management infrastructure for Windows CCS 2003. Compute Cluster Pack includes Microsoft SQL Server 2000 Desktop Engine to support the database requirements for Windows CCS 2003.

SQL Server 2000 Desktop Engine has some limitations. These limitations may make SQL Server 2000 Desktop Engine less suitable for use with cluster deployments of over 200 cluster nodes. Therefore, you may want to use a full version of SQL Server together with Windows CCS 2003. You can deploy a full version of SQL Server for use with Windows CCS 2003 by using one of the following methods:
  • Upgrade SQL Server 2000 Desktop Engine to SQL Server 2000.
  • Install a full version of SQL Server 2000 before you install the Compute Cluster Pack.
  • Install a full version of SQL Server 2005 before you install the Compute Cluster Pack.
This article contains step-by-step instructions for each of these deployments.
Back to the top

INTRODUCTION

This article describes how to upgrade to a full version of SQL Server for use with Windows Compute Cluster Server 2003 (Windows CCS 2003).
Back to the top

MORE INFORMATION

Overview

Windows CCS 2003 is a High Performance Computing (HPC) solution from Microsoft. Windows CCS 2003 is designed to help reduce user time-to-insight for HPC workloads. To do this, Windows CCS 2003 uses an existing Windows-based IT infrastructure for management, security, storage, and desktop use. Windows CCS 2003 provides an integrated cluster environment that includes the operating system, a job scheduler, Message Passing Interface (MPICH-2) support, cluster management components, and cluster monitoring components. Windows CCS 2003 consists of the following two parts:
  • A 64-bit version of Windows Server 2003
  • Microsoft Compute Cluster Pack (CCP)

    This component is a combination of interfaces, tools, and a management infrastructure.

SQL Server 2000 Desktop Engine

Compute Cluster Pack includes SQL Server 2000 Desktop Engine to support the database requirements for Windows CCS 2003. The database is used to store cluster configuration information, job information, security-related information, and other user information.

Limitations in SQL Server 2000 Desktop Engine may make it less suitable for use with large cluster deployments, such as deployments of over 200 cluster nodes. These limitations include the following:
  • The maximum number of processors in the host computer is restricted to two.
  • Maximum RAM is limited to 2 gigabytes (GB).
  • Maximum database size is restricted to 2 GB.
  • A workload governor may restrict performance when many connections are made to the database.

    For more information about the workload governor, visit the following Microsoft Web site:
    http://msdn2.microsoft.com/en-us/library/aa224554(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa224554(SQL.80).aspx)
    For more information about how to upgrade the workload governor, visit the following Microsoft Web site:
    http://msdn2.microsoft.com/en-us/library/aa224741(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa224741(SQL.80).aspx)

64-bit computing

With the introduction of 64-bit support in SQL Server 2005, you can combine the power of a 64-bit operating system together with the 64-bit version of SQL Server. The advantages of a 64-bit computing environment include the following:
  • A larger addressable memory space is available.
  • 64-bit processors provide enhanced parallelism. They also scale better by yielding stronger returns per processor than 32-bit processors.
  • An improved bus architecture improves performance by moving more data between the cache and the processors in a shorter period.
  • A larger processor on-die cache allows for faster completion of user requests and for more efficient use of processor time.
For more information about the advantages of a 64-bit environment, visit the following Microsoft Web site:
http://www.microsoft.com/sql/techinfo/whitepapers/advantages-64bit-environment.mspx (http://www.microsoft.com/sql/techinfo/whitepapers/advantages-64bit-environment.mspx)
Windows CCS 2003 takes advantage of the full version of SQL Server. This includes the 64-bit versions of SQL Server 2005.
Back to the top
Note You must install a 64-bit version of SQL Server on a full version of Microsoft Windows Server 2003. Windows Server 2003 Compute Cluster Edition does not support the installation of a full version of SQL Server. For more information, visit the following Microsoft Web site:
http://technet2.microsoft.com/WindowsServer/en/library/2a4807d9-92d1-4183-8e3b-4ff20aeebce21033.mspx?mfr=true (http://technet2.microsoft.com/WindowsServer/en/library/2a4807d9-92d1-4183-8e3b-4ff20aeebce21033.mspx?mfr=true)
Back to the top

To use a full version of SQL Server together with Windows Compute Cluster Server 2003

You can upgrade SQL Server 2000 Desktop Engine to SQL Server 2000, to SQL Server 2005 Express Edition, or to SQL Server 2005 Workgroup Edition. However, these versions of SQL Server include limitations that may affect the Windows CCS 2003 environment. Therefore, this article only discusses how to install the full versions of SQL Server 2000 and of SQL Server 2005.

To upgrade SQL Server 2000 Desktop Engine to SQL Server 2000

To upgrade SQL Server 2000 Desktop Engine to SQL Server 2000, you must have an appropriately licensed version of SQL Server 2000 and SQL Server 2000 Service Pack 4 (SP4).

Note You must apply SQL Server 2000 SP4 after you perform the upgrade operation.

To upgrade SQL Server 2000 Desktop Engine to SQL Server 2000 Standard Edition, follow these steps:
  1. To access the SQL Server 2000 installation files, insert the SQL Server 2000 CD, or connect to a network location. If you insert the SQL Server 2000 CD, you receive a message that states that to install SQL Server 2000 on a 64-bit operating system, you must run the Setupsql.exe file. This file is located in the x86\Setup folder on the SQL Server 2000 CD. When you run this program, you receive a message that states that you must install SQL Server 2000 SP4 after the installation of SQL Server 2000 is complete.
  2. Follow the steps in the SQL Server 2000 Setup program. You can use the default installation settings except for the following:
    • On the Computer Name page

      Verify that the Head Node name appears in the Or, enter the name of a new or existing Virtual SQL Server to manage box. Also, leave the default Local Computer option selected.
    • On the Installation Selection page

      Click Upgrade, remove, or add components to an existing instance of SQL Server.
    • On the Instance Name page

      Verify that the COMPUTECLUSTER named instance appears in the Instance name list. This is the instance that you want to upgrade.
    • On the Existing Installation page

      Leave the default Upgrade your existing installation option selected.
    • On the Upgrade page

      Click to select the Yes, upgrade my programs check box.
    • On the Choose Licensing Mode page

      Verify that the appropriate licensing option is selected. If you click Per Seat for, make sure that you have a sufficient number of connections configured to support the cluster.
    • When you receive the following message, click Yes:
      Do you want to install additional components?
      You must click Yes to install the SQL Server Management Tools.

      Note If you do not want to install the SQL Server 2000 Management Tools, you may click No at this message.
  3. Follow the remaining steps in the Setup program to install SQL Server 2000.
  4. After the upgrade operation is complete, install SQL Server 2000 SP4.
  5. Use the Server Network Utility to enable the appropriate protocols to let you connect to the instance of SQL Server. For example, you may have to use SQL Server Enterprise Manager to connect to the COMPUTECLUSTER named instance to view the database information.
  6. After you enable these protocols, stop and then start the SQL Server service (MSSQL$COMPUTECLUSTER) to let the changes take effect.

    Note When you restart the SQL Server service, you receive a message that states that the following services will also be restarted:
    • Microsoft Compute Cluster Management service
    • Microsoft Compute Cluster SDM Store service
    • Microsoft Compute Cluster Scheduler service
  7. After all the services have been restarted, run SQL Server Enterprise Manager, and then verify that you can view the CCPClusterService database information.

To install a full version of SQL Server 2000 before you install the Compute Cluster Pack

To install SQL Server 2000 before you install the Compute Cluster Pack, you must have an appropriately licensed version of SQL Server 2000 and SQL Server 2000 Service Pack 4 (SP4). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211  (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack

To install SQL Server 2000, follow these steps:
  1. To access the SQL Server 2000 installation files, insert the SQL Server 2000 CD, or connect to a network location. If you insert the SQL Server 2000 CD, you receive a message that states that to install SQL Server 2000 on a 64-bit operating system, you must run the Setupsql.exe file. This file is located in the x86\Setup folder on the SQL Server 2000 CD. When you run this program, you receive a message that states that you must install SQL Server 2000 SP4 after the installation of SQL Server 2000 is complete.
  2. Follow the steps in the SQL Server 2000 Setup program. You can use the default installation settings except for the following:
    • On the Computer Name page

      Verify that the Head Node name appears in the Or, enter the name of a new or existing Virtual SQL Server to manage box. Also, leave the default Local Computer option selected.
    • On the Installation Selection page

      Click Create a new instance of SQL Server, or install Client Tools.
    • On the Installation Definition page

      Verify that the Server and Client Tools option is selected.
    • On the Instance Name page

      Click to clear the Default check box, and then, type COMPUTECLUSTER in the Instance name box.
    • On the Setup Type page

      You can accept the default location of the SQL Server files or select a new location for the files, depending on the storage locations that are configured on the computer.
    • On the Choose Licensing Mode page

      Verify that the appropriate licensing option is selected. If you click Per Seat for, make sure that you have a sufficient number of connections configured to support the cluster.
  3. Follow the remaining steps in the Setup program to install SQL Server 2000.
  4. After the installation of SQL Server 2000 is complete, start the SQL Server Enterprise Manager program to view the default databases that are installed in the COMPUTECLUSTER named instance.
  5. Install SQL Server 2000 SP4 to the head node.
When you install Compute Cluster Pack, the installation program detects that a full version of SQL Server is installed. Also, the Compute Cluster Pack installation detects that the correct instance of SQL Server is installed. When you start SQL Server Enterprise Manager after the installation is complete, the CCPClusterService database is listed together with the default databases in the COMPUTECLUSTER named instance.

To install a full version of SQL Server 2005 before you install the Compute Cluster Pack

To install SQL Server 2005 before you install the Compute Cluster Pack, you must have an appropriately licensed version of SQL Server 2005 together with SQL Server 2005 Service Pack 1 (SP1). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913089  (http://support.microsoft.com/kb/913089/ ) How to obtain the latest service pack for SQL Server 2005

Note Because of the new security model that is introduced in SQL Server 2005, you may have to prepare other components for the installation of SQL Server 2005. For example, you may have to install Microsoft ASP.NET. These preparations depend on the particular SQL Server 2005 features that you want to install. For more information about how to install SQL Server 2005, see the SQL Server 2005 Books Online. To do this, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/ms130214.aspx (http://msdn2.microsoft.com/en-us/library/ms130214.aspx)
To install SQL Server 2005, follow these steps:
  1. Insert the SQL Server 2005 CD or connect to a network location to access the SQL Server 2005 installation files. If you want to install SQL Server 2005 from a shared network location, you must run the Setup.exe program in the Servers folder.
  2. Follow the steps in the SQL Server 2005 Setup program. You can use the default installation settings except for the following:
    • On the Components to Install page

      At a minimum, click to select the following check boxes:
      • The SQL Server Database Services check box
      • The Workstation components, Books Online and development tools check box

        Note If you do not install this component, SQL Server Management Studio is not installed.
    • On the Instance Name page

      Click Named instance, and then, type COMPUTECLUSTER in the Named instance box.
  3. Follow the remaining steps in the Setup program to install SQL Server 2005.
  4. After the installation of SQL Server 2005 is complete, install SQL Server 2005 SP1.
  5. After the installation of SQL Server 2005 SP1 is complete, verify that the appropriate protocols are enabled to let SQL Server Management Studio connect to the COMPUTECLUSTER named instance. To do this, follow these steps:
    1. Start the SQL Server Configuration Manager tool. To do this, click Start, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.
    2. Expand SQL Server 2005 Network Configuration, and then click Protocols for COMPUTECLUSTER.
    3. In the results pane, verify that the appropriate protocols are enabled. For example, verify that Shared Memory is enabled and that TCP/IP is enabled.
  6. Install Compute Cluster Pack.
When you install Compute Cluster Pack, the installation program detects that a full version of SQL Server is installed. Also, the Compute Cluster Pack installation detects that the correct instance of SQL Server is installed. When you start SQL Server Management Studio after the installation is complete, the CCPClusterService database is listed.
Back to the top

REFERENCES

For more information, visit the following Microsoft Web sites.

Windows Compute Cluster Server 2003
http://www.microsoft.com/windowsserver2003/ccs/default.mspx (http://www.microsoft.com/windowsserver2003/ccs/default.mspx)
Compute Cluster Server
http://technet2.microsoft.com/windowsserver/en/technologies/featured/ccs/default.mspx (http://technet2.microsoft.com/windowsserver/en/technologies/featured/ccs/default.mspx)
SQL Server
http://www.microsoft.com/sql/default.mspx (http://www.microsoft.com/sql/default.mspx)
SQL Server TechCenter
http://technet.microsoft.com/en-us/sqlserver/default.aspx (http://technet.microsoft.com/en-us/sqlserver/default.aspx)
SQL Server Developer Center
http://msdn2.microsoft.com/en-us/sql/default.aspx (http://msdn2.microsoft.com/en-us/sql/default.aspx)
SQL Server 2000 scalability
http://msdn2.microsoft.com/en-us/library/aa224748(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa224748(SQL.80).aspx)
SQL Server 2005 on a 64-bit platform
http://www.microsoft.com/sql/editions/64bit/default.mspx (http://www.microsoft.com/sql/editions/64bit/default.mspx)
Back to the top
APPLIES TO
  • Microsoft Windows Server 2003 Compute Cluster Edition
Back to the top
Keywords: 
kbdeployment kbhowto kbinfo KB930057
Back to the top
 

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations