0% found this document useful (0 votes)
2 views

To upgrade a SQL Server failover cluster

The document outlines the step-by-step process for upgrading a SQL Server failover cluster, starting from inserting the installation media and running Setup.exe. It includes important instructions regarding prerequisites, instance selection, feature selection, and monitoring the upgrade progress across all nodes. After completing the upgrade on one node, the same steps must be repeated for all other nodes in the cluster to finalize the upgrade process.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views

To upgrade a SQL Server failover cluster

The document outlines the step-by-step process for upgrading a SQL Server failover cluster, starting from inserting the installation media and running Setup.exe. It includes important instructions regarding prerequisites, instance selection, feature selection, and monitoring the upgrade progress across all nodes. After completing the upgrade on one node, the same steps must be repeated for all other nodes in the cluster to finalize the upgrade process.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

To upgrade a SQL Server failover cluster

1. Insert the SQL Server installation media, and from the root folder, double-click
Setup.exe. To install from a network share, move to the root folder on the share, and
then double-click Setup.exe. You may be asked to install the prerequisites, if they are
not previously installed.

2. Windows Installer 4.5 is also required, and may be installed by the Installation
Wizard. If you are prompted to restart your computer, restart and then start
Setup.exe again.

Important:
For more information about steps 3 and 4, see the Best Practices Before Upgrading
Failover Cluster section.

3. After prerequisites are installed, the Installation Wizard starts the SQL Server
Installation Center. To upgrade an existing instance of SQL Server 2008, click
Upgrade from SQL Server 2000 or SQL Server 2005.

4. If Setup support files are required, SQL Server Setup installs them. If you are
instructed to restart your computer, restart before you continue.

5. The System Configuration Checker runs a discovery operation on your computer. To


continue, click OK. At this point, Setup log files are created for your installation. For
more information about log files, see How to: View and Read SQL Server Setup Log
Files.

6. On the Language Selection page, you can specify the language for your instance of
SQL Server if you are installing on a localized operating system and the installation
media includes language packs for both English and the language corresponding to
the operating system. For more information about cross-language support and
installation considerations, see Local Language Versions in SQL Server.

To continue, click Next.

7. On the Product Key page, enter the PID key for the new version edition that matches
the edition of the old product version. For example, to upgrade an Enterprise failover
cluster, you must supply a PID key for SQL Server 2008 Enterprise. Click Next to
continue. Be aware that the PID key that you use for a failover cluster upgrade must
be consistent across all failover cluster nodes in the same SQL Server instance. For
more information, see Editions and Components of SQL Server 2008 R2 and Version
and Edition Upgrades.

8. On the License Terms page, read the license agreement, and then select the check
box to accept the license terms and conditions. To help improve SQL Server, you can
also enable the feature usage option and send reports to Microsoft. Click Next to
continue. To end Setup, click Cancel.

9. On the Select Instance page, specify the SQL Server instance to upgrade to SQL
Server 2008. Click Next to continue.

10. On the Feature Selection page, the features to upgrade are preselected. A
description for each component group appears in the right pane after you select the
feature name. Be aware that you cannot change the features to be upgraded, and
you cannot add features during the upgrade operation. To add features to an
upgraded instance of SQL Server 2008 after the upgrade operation is complete, see
How to: Add Features to an Instance of SQL Server 2008 R2 (Setup).
11. On the Instance Configuration page, fields are automatically populated from the old
instance. You can choose to specify the new InstanceID value.

Instance ID - By default, the instance name is used as the Instance ID. This is used
to identify installation directories and registry keys for your instance of SQL Server.
This is the case for default instances and named instances. For a default instance,
the instance name and instance ID would be MSSQLSERVER. To use a nondefault
instance ID, select the Instance ID check box and provide a value. If you override
the default value, you must specify the same Instance ID for the instance being
upgraded on all the failover cluster nodes. The Instance ID for the upgraded instance
must match across the nodes.

Detected instances and features - The grid shows instances of SQL Server that
are on the computer where Setup is running. Click Next to continue.

12. The Disk Space Requirements page calculates the required disk space for the
features that you specify, and compares requirements to the available disk space on
the computer where Setup is running. For more information, see Disk Space
Requirements.

13. On the Full-Text Search Upgrade page, specify the upgrade options for the databases
being upgraded. For more information, see Full-Text Search Upgrade Options.

14. On the Error Reporting page, specify the information that you want to send to
Microsoft to help improve SQL Server. By default, option for error reporting is
enabled. For more information, see Error Reporting.

15. The System Configuration Checker runs one more set of rules to validate your
computer configuration with the SQL Server features that you have specified, before
the upgrade operation begins.

16. The Cluster Upgrade Report page displays the list of nodes in the failover cluster
instance and the instance version information for SQL Server components on each
node. It displays the database script status and replication script status. In addition, it
also displays informational messages on what will occur when you click Next.
Depending on the number of failover cluster nodes that have already been upgraded
and total number of nodes, Setup displays the failover behavior that happens when
you click Next. It also warns about potential unnecessary downtime if you have not
installed the prerequisites already.

17. The Ready to Upgrade page displays a tree view of installation options that were
specified during Setup. To continue, click Upgrade.

18. During upgrade, the Progress page provides status so that you can monitor the
upgrade progress on the current node as Setup continues.

19. After the upgrade of the current node, the Cluster Upgrade Report page displays an
upgrade status information for all the failover cluster nodes, features on each failover
cluster node, and their version information. Confirm the version information that is
displayed and continue with the upgrade of the remaining nodes. If the failover to
upgraded nodes occurred, this is also apparent on the status page. You can also
check in the Windows Cluster administrator tool to confirm.

20. After upgrade, the Complete page provides a link to the summary log file for the
installation and other important notes. To complete the SQL Server installation
process, click Close.

21. If you are instructed to restart the computer, do so now. It is important to read the
message from the Installation Wizard when you have finished with Setup. For more
information about Setup log files, see How to: View and Read SQL Server Setup Log
Files.

22. To complete the upgrade process, repeat steps 1 to 21 on all the other nodes on the
SQL Server failover cluster.

You might also like