SQL Server 2022 had a rocky start to put it kindly. It barely shipped by the end of 2022, features were missing, and it took months before the first Cumulative Update even shipped.
I’m here to tell you that 2022 is back, baby!
Cumulative Update 3 just dropped, and Microsoft is right back on track with their claimed servicing schedule, which says that SQL Server is supposed to get a CU per month for the first year of its release. That’s awesome – but wait, there’s more – or rather, less! There are only 9 issues that were fixed in this CU, and because there are so few, I’m gonna list ’em all:
- SSAS fails when you rename partitions to an existing name
- Security vulnerabilities CVE-OU812 and CVS-PRESCRIPTION
- Memory leak when using log shipping with In-Memory OLTP
- Updated error message when you create an external table
- Better filter predicate pushdowns for PolyBase
- Less change tracking memory dumps
- Linux mssql-conf commands were giving error messages even when they succeeded (how Linux-y)
- New feature to parallelize the version cleaner for PVS, and
- It wouldn’t be a CU without more fixes to the notoriously buggy scalar function inlining (and also, even more instances where that “feature” is now simply turned off)
Folks, that list is incredibly short, kinda like the list of memorable quotes from How Stella Got Her Groove Back, a movie that I never actually watched. I can only come to one conclusion: SQL Server 2022 is ready for widespread deployment!
Well, I mean, as soon as they finish working on the features. Managed Instance Link is still only in private preview. That particular woman is still finding her groove.
In related news, SQL Server 2019 got CU20 as well. That one has more than 9 fixes in it, many of which aren’t included in the SQL Server 2022 CU3 fix list. I’m sure that means that SQL Server 2022 is invulnerable to those bugs. </s>
Hey now, I went to Jamaica because of that movie. 🙂
That’s not a bad choice at all!