On June 15, 2023, Microsoft released SQL Server 2022 Cumulative Update 5. This is Build 16.0.4045.3. By Microsoft’s count, there are 31 public fixes and improvements in this CU, so it has about an average number of fixes.
It is always a good idea to read through the CU KB article to see more information about each fix and improvement. There are several interesting fixes in this CU.
This fifth SQL Server 2022 CU is once again “on-time” (based on Microsoft’s public guidance about how SQL Server is serviced), so kudos again to Microsoft!
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 usually only get security updates.
No Service Packs for SQL Server 2022
SQL Server 2017 and newer does not have any Service Packs. Microsoft is not using Service Packs any longer as a servicing mechanism for SQL Server, only cumulative updates.
Since SQL Server 2022 has been GA for less than a year, Microsoft is supposed to release a new CU every month. After the first year, this changes to a new CU every two months, until SQL Server 2022 falls out of Mainstream Support on January 11, 2028. When SQL Server 2022 falls out of Mainstream Support, there won’t be any more cumulative updates, only security fixes.
SQL Server cumulative updates are actually cumulative, which might seem obvious from the name. This means that when you install SQL Server 2022 CU5, you get all the previous updates.
Despite some stumbles by Microsoft, I am still a 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 2022 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!