Sql-server – Apply SQLServer Service Pack to a Single Node Cluster

clusteringpatchingsql serversql server 2014sql-server-2008-r2

I have to apply a SQL Server 2008 R2 Service Pack to a Single Node Cluster.

The other node died and new hardware has been ordered.

Is there anything weird to worry about?

Normally we'd apply the service pack to the passive node first, then failover, and apply the service pack to the newly passive node, however this clust only has 1 node. We're loading Service Pack 2 so we can upgrade to SQL Server 2014.

Best Answer

Nothing particular to worry about, but you will incur downtime as the SP runs its stuff in "script mode" during which users cannot connect.

It might go without saying, but I'd ensure you have a valid (i.e. tested) backup of the databases (including the system databases) on the affected system prior to doing any patching, whether on a single-node cluster, a multi-node cluster, or even a stand-alone instance. You can never have too many backups.

Related Solutions

SQL Server 2012 – Is Service Pack 2 Installed on Passive Node?

The logs led us to review our Cluster services:

There was an error to lookup cluster resources. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 4104. Description: .
HResult : 0x86d80014
FacilityCode : 1752 (6d8)
ErrorCode : 20 (0014)
Data:
    errorMessage = There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 4104. Description: .

We determined that the replication agent service was the cause of the incomplete installation.

We removed the service from Cluster Resources and re-applied SP2 without success. We stopped the service on the node and re-applied SP2 without success.

Error: Failed to run patch request for instance: MSSQLSERVER (exit code: -2032664552)

We uninstalled the service from the server nodes, and then successfully "re-applied" SP2.

Follow-up actions:

We'll be contacting the replication agent vendor to discuss why this was required.
Review the Microsoft document "Patching SQL Server Failover Cluster Instances with Cluster-Aware Updating (CAU)", available here, which I discovered today.

Fix Reporting Service 2014 SP1 Error – Wrong Database Version

There are two workarounds:

Delete one record from table ServerUpgradeHistory

USE [name_of_you_SSRS_database]

DELETE FROM ServerUpgradeHistory WHERE ServerVersion = 163

Install Cumulative Update 1 for SQL Server 2014 Service Pack 1. Before updating your SQL Server 2014 SP1 with Cumulative Update 1 - test it hard in your lab.

BE AWARE - Pay attention to backup encryption keys before you upgrade SSRS 2012 to 2014. After you apply CU1 all your encrypted content will be inaccessible.

Best Answer

Related Solutions

SQL Server 2012 – Is Service Pack 2 Installed on Passive Node?

Fix Reporting Service 2014 SP1 Error – Wrong Database Version

Related Question