SQL SERVER 2019 Cumulative and Security updates

[Koldov]

Well I did a thing on my WSUS server on Friday (saw that I could check for SQL updates)...

 

For some reason I have (to my shame) never really taken any notice of SQL (other than knowing it had to be installed for SIMS etc.).

 

Anyway, I've come in this morning to 33 updates waiting for approval!

 

Due to having always been on WSUS (and never having the SQL 'Product' ticked) it's never been something that's pinged up on my radar (or even crossed my mind).

 

So, out of the 33 updates awaiting approval, which do I approve? Is it OK (as with Windows updates) just to approve the latest CU (as that should have all previous updates in) and security patch?

 

Also, I've always heard SQL is a bit of a nightmare when it goes wrong (probably why I've never messed with updating it, but I'm hoping it's improved over the years) so any 'gotchas' or other advice, apart from having a good backup...

 

 

EDIT: Alternatively 'Approve' them all and let '$deity' sort them out?

Edited March 25, 2024 by Koldov

[3s-gtech]

As they're CUs, you may not be able to jump all versions. Have a check, you may need to update in stages.

 

I always let SQL Server update via WSUS without issues, but make sure your backups are solid - VM and database. You want to be able to go back to a snapshot if necessary (I did this a couple of times with failed SIMS server in-place upgrades).

[pete]

^ I'd add the "if it's a SQL server for SIMS (or cashless catering), stop any third-party (or SIMS) services that interact with SQL" caveat.

 

As one of them won't stop properly when it's asked to for the patch to install cleanly.

[Koldov]

Well, this escalated quickly...

 

After I added SQL server into my WSUS and all the updates appeared, the servers checked in one by one but none of them appeared to want the updates!

 

In fact all the updates are showing that WSUS has checked and are now sitting with a status of Installed/Not Applicable for all the servers...

 

Initially I thought that meant I was all up to date, but a bit more research on patch levels for SQL showed I wasn't and now I come across this piece of information!

 

It appears my SQL is on a GDR (General Distribution Release) branch. Therefore it isn't on a CU branch and won't look for other CUs until I manually patch it with a CU first... as it has had the latest GDR only update (currently sitting at 15.0.2104.1)

 

"Cumulative Updates: The MU detection logic now allows clean instances that are at the baseline (RTM or SP, with no servicing updates) or that are already updated along the CU branch to receive the update. A CU update does not have to be installed for an instance to be offered the update. However, if the instance has a GDR update, the instance must still be manually updated outside MU to become manageable through MU (WSUS) automation."

 

"For SQL Server 2019, the RTM baseline can be either the RTM (15.0.2000.5) version baseline or the RTM + RTM GDR (15.0.2070.41) version baseline. Either version will work for this release".

 

https://learn.microsoft.com/en-us/troubleshoot/sql/releases/new-mu-servicing-model