Note the following information before you install SQL Server 2005 SP3 on a failover cluster instance:
Do not stop the cluster service before you run the SP3 Setup program, or while the installation program is running.
Do not end any running processes before you run the SP3 Setup program.
Do not take the SQL Server service off line before you run the SP3 Setup program. The SP3 Setup program will stop and start the SQL Server service.
Run the SP3 Setup program on the primary node of the failover cluster instance.
You must restart all failover cluster nodes after SP3 is finished installing.
Rolling upgrade is not supported for SP3.
Failover Cluster Installation
The following information applies only to SQL Server 2005 components that are part of a failover cluster.
To install the service pack on a failover cluster:
To ensure that SQL Server 2005 SP3 will be installed on all nodes of a failover cluster instance, verify that the TASK Scheduler is running on all passive nodes of your failover cluster instance.
If any resources have been added that have dependencies on SQL Server resources, those dependencies must either be removed or taken offline before you install SQL Server 2005 SP3. If you do not remove the dependencies, the installation of SP3 will take those resources offline.
When a clustered resource is taken offline, all dependent resources are also taken offline by the cluster service.
Run the SQL Server 2005 SP3 executable package file from the active node that owns the group containing the failover cluster instance that you plan to upgrade. This installs the service pack files on all nodes in the failover cluster. You cannot install SP3 from any passive nodes in the failover cluster.
On the Feature Selection page of the SQL Server 2005 SP3 Setup Wizard, select the failover cluster instance that you plan to upgrade. Setup will prompt you for the login credentials that are used to connect to other nodes in the cluster.
Keep all nodes of the cluster online during Setup. This ensures that the upgrade is applied to each cluster node.
If you removed dependencies or took resources offline in step 1, restore the dependencies, or bring the resources online.
Setup might require you to restart the failover cluster nodes. This restart replaces the files that were in use during Setup.