How to Patch SQL Server 2019

This video shows you how to patch SQL Server 2019 with a Cumulative Update and explains why it is important. It includes how to find the latest Cumulative Update and how to determine whether you need it or not.
Why Should You Patch SQL Server?
glennsqlperformance.com/2021/...
KB4518398 - SQL Server 2019 build versions
learn.microsoft.com/en-us/tro...
⏱️TIMESTAMPS⏱️
0:00 Intro
0:15 Why would you want to do this?
0:44 How Microsoft maintains SQL Server
2:26 What is in the CU?
3:21 Downloading SQL Server 2019 Cumulative Update 21
3:48 Checking your CU level
4:45 Checking the default file paths
5:41 Installing the cumulative update
8:55 Checking to see if the CU was installed
9:38 Outro
9:56 Bonus Chorizo footage!
🔴 Please subscribe for more content like this!
Links to Amazon are typically monetized on my channel (affiliate links) and may return a commission of sales to me from the retailer. This is unrelated to the product manufacturer.
SOCIAL
===============================
📝 - BLOG: glennsqlperformance.com/
🐦 - TWITTER: / glennalanberry
👥 - FACEBOOK: / glenn.berry.92
LinkedIn: / glberry
Host, Video: Glenn Berry

[@huskesh]

Sir loved your channel, the views may be less but we love your of explaining thing ❤❤❤❤

[@GlennBerrySQL]

Thanks!

[@kishortala2950]

Great video Glenn. Very helpful tutorial. Cheers to Chorizo ❤

[@GlennBerrySQL]

Thank you! Chorizo says hello!

[@DB-sf1hy]

Another idea: How to make SSMS start up faster on corporate workstation? Sometimes it takes me several minutes to start up SSMS. I noticed your SSMS was ready immediately

[@GlennBerrySQL]

You want to make sure you are using SSMS 19.1 rather than any earlier version. Microsoft made some performance optimizations in 19.1 (and in 19.0) that help cold startup performance. SSMS 19.1 is about 15-25% faster for cold startup performance than SSMS 18.12.1.
glennsqlperformance.com/2023/05/30/ssms-19-1-performance-improvements/
SSMS is CPU-bound during cold startup. The real way to make SSMS startup more quickly is to have a faster CPU, with more cores. I realize that you don't have much control over this with a corporate workstation...

[@sackos6573]

Great video! Can I install CU on top of GDR build?

[@GlennBerrySQL]

Yes, as long as it is a newer build.

[@pankaj2443]

Pls make video on HA server patching .

[@GlennBerrySQL]

Thanks for the suggestion.

[@fabioantonioberti]

Thanks for the video. I have a question, for an environment that has a Cluster of 2 VMs with Always ON, what care should I take when patching? Which VM is recommended to start, primary or secondary? If I start with the primary, should I force manual failover to the secondary VM?

[@GlennBerrySQL]

With an AG, you should always patch the Secondary replica first. Then, after it is done and all the databases in the AG are Synchronized, you can do a Manual Failover to the original Secondary and repeat the process on the other node. Then, after it is done and all the databases in the AG are Synchronized, you can do a Manual Failover back to the original Primary.

[@fabioantonioberti]

@@GlennBerrySQL Thanks for the answer.

[@RadekGaska]

Hello Glenn, Could you please advise rollback plan for patching? Is it necessary to take VM's snapshots, SQL backups etc or it does not make any sense for patching activities?

[@ChorizoBerry]

You can uninstall a SQL Server Cumulative Update. If you wanted to be more thorough, you could take VM snapshots, backup all of your databases, script out logins and other instance-level objects, etc.

[@GlennBerrySQL]

You can uninstall a SQL Server CU.

[@roblochon1276]

@@GlennBerrySQL Sure . .but on my machine an update of sql2016 destroy the master database i don't know why .. sql server doesn't start again ... The only solution is to rebuild systems database .. it's not so easy and i can't imagine on a production database at the end of the night .

[@GlennBerrySQL]

@@roblochon1276 I'm sorry that happened to you. There is always a chance that a software update will break something, but it does not happen very often with SQL Server. Being careful and being prepared for a worst-case scenario is always a good idea. OTOH, never updating SQL Server because it might cause a problem is not the solution either.

[@smf00027]

Sir no need to stop all sql services?

[@GlennBerrySQL]

The CU setup program automatically shuts down the SQL Server Service during the installation.