SQL Server Service Pack Installation – Impact on Other Instances

service-packsql serversql-server-2016

I have a SQL Server 2016 with an instance A and an instance B. Both have SP1 installed, no reporting server.

Can I assume that, when I install SP2 on instance B only, that, while installing, the running of instance A will not be hindered ? (no restarting of the SQL Server service)

Since sqlbrowser is a shared feature, it will also be updated, will this hinder any remote access to instance A (fix port) for the time of the install?

Best Answer

The Service Pack installation process will identify if there are any files in use that will necessitate a restart of the server.

Each instance has it's own independent set of executables, so instance B should not be affected by installation of a new service pack on instance A.

The SQL Server Browser Service will be restarted pretty quickly, however there may be a short period of time where name resolution for named instances may not work as expected.

Best practice for this kind of work on a production server is to schedule it to occur during a period of low or no activity.

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.

Sql-server – Can’t uninstall Microsoft SQL Server 2016 RC3

Thanks to Aaron Bertrand, I was able to resolve the issue following the manual steps outlined in his blog:

Fun with software : uninstalling SQL Server 2008 R2 Evaluation Edition

...in spite of the title, it's not just for 2008 R2 or Evaluation Edition.

In case the link ever stops working, the essential steps are:

Locate SQL Server related GUIDs under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\

Also look for GUIDs in folders under Uninstall called e.g. "Microsoft SQL Server 2008 R2"
Run for each item:
```
msiexec /x "{guid}"
```

Best Answer

Related Solutions

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

Sql-server – Can’t uninstall Microsoft SQL Server 2016 RC3

Related Question