If you’re one of the relatively few folks running SQL Server 2022 in production, the rest of us appreciate your beta testing. You’ve got a new update to apply, though, because Cumulative Update 14 is out with some wild fixes:
- VSS backups can fail if you’ve previously deleted a database
- The SQL Server Launchpad service can’t shut down
- Availability Groups replicas show “Not Synchronizing” for several minutes after a “successful” failover
- On Linux, SQL Server may ignore memory limits
- Plan cache leaks and access violations due to Cardinality Estimation feedback race conditions
- Change Tracking auto cleanup burns CPU even when CT isn’t enabled
This one’s looking like a must-apply update. Go get ’em!
3 Comments. Leave new
I didn’t even get a T-shirt for joining this “SQL Server 2022 GA” limited beta program.
I don’t see SQL2022 is in RTM-beta state as some of our clients are using SQLSERVER 2022 for real time SAP transactions ever since it was RTM. So far no issue encountered which has effected our client business. Is there anything in the world flawless…?! We read only what is mentioned in release notes but there are other tons of fixes inside every CU. I found MS documentation much better and transparent than other leading database providers. Atleast MS is proactively acknowledging and fixing the issue in a timely fashion. Even Boeing Aircraft has flaws. So assuming SQL2022 is still in RTM-beta state is incorrect assumption.
OK