Figure 8: The Select Features page of the Install a SQL Server 2008 Patch dialog box for a cumulative update After you have updated the first passive node, you can repeat the same installation steps if other passive nodes form part of your first round of planned updates. For example, if you have a four-node cluster, and you are updating two passive nodes, you would repeat the update process for each of the two passive nodes that were removed as potential hosts of the SQL Server instance. After you have completed the updates to the passive nodes, in the Failover Cluster Management tool, in the SQL Server network resource, on the Advanced Policies tab, you should reselect the updated nodes to enable hosting of the SQL Server instance. After you have re-enabled the updated nodes, you can then fail over the SQL Server instance from the node that has not been updated to an updated node. After failover to the updated node, update scripts automatically run against the engine. You can use the Failover Cluster Management tool to confirm that the SQL Server instance resources came online on the newly updated node. Then, you can confirm the version number of the SQL Server instance by
Figure 8: The Select Features page of the Install a SQL Server 2008 Patch dialog box for a cumulative update After you have updated the first passive node, you can repeat the same installation steps if other passive nodes form part of your first round of planned updates. For example, if you have a four-node cluster, and you are updating two passive nodes, you would repeat the update process for each of the two passive nodes that were removed as potential hosts of the SQL Server instance. After you have completed the updates to the passive nodes, in the Failover Cluster Management tool, in the SQL Server network resource, on the Advanced Policies tab, you should reselect the updated nodes to enable hosting of the SQL Server instance. After you have re-enabled the updated nodes, you can then fail over the SQL Server instance from the node that has not been updated to an updated node. After failover to the updated node, update scripts automatically run against the engine. You can use the Failover Cluster Management tool to confirm that the SQL Server instance resources came online on the newly updated node. Then, you can confirm the version number of the SQL Server instance by
SQLServer2008FailoverCluster.docx