Timeline for Updating SQL Server 2016SP2 to latest CU in Cluster...what happens?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16, 2020 at 16:30 | vote | accept | regular_joe | ||
| Jul 16, 2020 at 13:16 | comment | added | regular_joe | Thank you again for the info and feedback this is super useful. Unfortunately, it's a two node cluster, so it's my only partner. | |
| Jul 16, 2020 at 3:53 | comment | added | AMtwo | In addition to this, you should remove the server you're patching from being a possible failover partner while the CU installs. In the event there's a failover during install, this can result in your instance being unable to start, and forcing you to repair the install and restore system databases. | |
| Jul 15, 2020 at 20:57 | comment | added | StrayCatDBA | no, it won't do anything strange. | |
| Jul 15, 2020 at 20:07 | comment | added | regular_joe | Hey, thanks for the feedback on this I really appreciate it. Do I have to worry about SQL Server kicking on during any of this on the passive nodes? Just trying to make sure I don't miss any steps. We're moving up like five cu's from where we are now | |
| Jul 15, 2020 at 19:32 | history | answered | StrayCatDBA | CC BY-SA 4.0 |