On April 11, 2024, Microsoft released SQL Server 2019 Cumulative Update 26. This is Build 15.0.4365.2 By Microsoft’s count, there are 19 public fixes or improvements in this CU, so it has a about an average number of fixes and improvements.
This CU is once again on time (based on Microsoft’s public guidance about how SQL Server is serviced), so kudos to Microsoft for staying on schedule for this CU. This CU also has the security fixes from the CU25 + GDR release from April 9, 2024.
It is always a good idea to read through the CU KB article to see more information about each fix and improvement. This will help you decide whether to push your organization to get the latest CU deployed or not. I have a blog post that might help you with this argument:
Personally, I think most organizations are far better off being on the “CU Train” rather than the “GDR Train”. With the CU Train, you get bug fixes, product improvements and security updates. On the GDR Train, you only get security updates in most cases.
How To Patch SQL Server 2019
I also have a YouTube video about 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 for SQL Server 2019 and how to determine whether you need it or not.
No Service Packs for SQL Server 2019
SQL Server 2017 and newer does not have Service Packs. Microsoft is not using Service Packs as a servicing mechanism for SQL Server, only cumulative updates.
Microsoft released a new CU every month for SQL Server 2019 for the first four months after GA. Due to human malware concerns, CU5 was delayed until June 22, 2020. From CU6 through CU8, they seemed to be back to a normal monthly release schedule.
Then Microsoft announced a release delay in order to give their employees some well deserved time off over the holidays. After that, there was silence until the Extended Events security update was released on January 12th, 2021.
Since SQL Server 2019 has been GA for more than a year, Microsoft has switched to releasing a new CU every two months. This is what they will do until SQL Server 2019 falls out of Mainstream Support on January 7, 2025. When SQL Server 2019 falls out of Mainstream Support, there won’t be any more cumulative updates.
Final Words
SQL Server cumulative updates are actually cumulative, which might seem obvious from the name. This means that when you install SQL Server 2019 CU26, you are going to get all of the hotfixes and product improvements from ALL of the previous CUs. Microsoft has fixed hundreds of bugs since SQL Server 2019 RTM, and they have also added a significant number of product improvements and new features since the RTM release.
Despite some stumbles by Microsoft (including SQL Server 2019 CU7), I am still a very big proponent of trying to keep your SQL Server instances as up to date as possible. That does not mean throwing a new CU into Production the day it is released, but it also does not mean avoiding patching SQL Server indefinitely either. You really are better off trying to stay as current as possible on your SQL Server builds.
Here is Microsoft’s official guidance:
- SQL Server CUs are certified to the same levels as Service Packs, and should be installed at the same level of confidence.
- Historical data shows that a significant number of support cases involve an issue that has already been addressed in a released CU.
- CUs may contain added value over and above hotfixes. This includes supportability, manageability, and reliability updates.
If you have any questions about this post, please ask me here in the comments or on Twitter. I am pretty active on Twitter as GlennAlanBerry. Thanks for reading!
Thank You Glenn for the post.
I wonder why you did not mention it is in fact the client that needs to be patched.
There is also an update for SSMS.
I am fan of your performance queries for a long time.
I have the feeling you know more. But it is sometimes wise not spread too much information.
Kind regards
My post was about SQL Server 2019 CU26 (which also includes the recent GDR security fixes). As you say, there has also been a security update for SSMS 20. Generally speaking, you would want to patch both SQL Server 2019 and SSMS 20, wherever they might be installed (client or server).