SQL Server 2022 CU14: Key Updates and Enhancements

# Announcing SQL Server 2022 CU14: A Must-Apply Update!

Hey there, SQL Server aficionados! If you’re among the brave souls running SQL Server 2022 in production, we salute you. Your adventurous spirit is paving the way for the rest of us, and now it’s time for another exciting update. Buckle up, because Cumulative Update 14 is here, and it’s packed with some wild fixes that you won’t want to miss.

## What’s New in CU14?

This update is like a superhero swooping in to save the day, addressing a variety of issues that have been causing headaches. Here’s a sneak peek at the highlights:

### 1. VSS Backups Can Fail if You’ve Previously Deleted a Database
Ever had that sinking feeling when your VSS backups fail? Well, if you’ve deleted a database in the past, this might have been the culprit. CU14 swoops in to fix this pesky issue, ensuring your backups run smoothly.

### 2. The SQL Server Launchpad Service Can’t Shut Down
Imagine trying to shut down the SQL Server Launchpad service, only to find it stubbornly refusing to comply. Frustrating, right? This update addresses that, making sure the service shuts down when you tell it to.

### 3. Availability Groups Replicas Show “Not Synchronizing” After a “Successful” Failover
Nothing says “false sense of security” like a failover that appears successful, only for your Availability Groups replicas to show “Not Synchronizing” for several minutes. CU14 steps in to resolve this, ensuring your replicas are truly in sync.

### 4. On Linux, SQL Server May Ignore Memory Limits
Linux users, rejoice! If SQL Server has been ignoring your memory limits, this update has your back. CU14 ensures that SQL Server respects the memory boundaries you’ve set, keeping your system running efficiently.

### 5. Plan Cache Leaks and Access Violations Due to Cardinality Estimation Feedback Race Conditions
Plan cache leaks and access violations can be a nightmare, especially when they’re caused by Cardinality Estimation feedback race conditions. CU14 tackles these issues head-on, bringing stability back to your SQL Server environment.

### 6. Change Tracking Auto Cleanup Burns CPU Even When CT Isn’t Enabled
Is your CPU working overtime because of Change Tracking auto cleanup, even when CT isn’t enabled? CU14 puts an end to this unnecessary CPU usage, giving your processors a well-deserved break.

## Time to Update!

With all these fixes, CU14 is looking like a must-apply update. Don’t wait—head over to the Microsoft update page to get all the details and download the update. For a broader overview of SQL Server builds, you can also check out SQL Server Builds.

So, what are you waiting for? Go get ’em, and keep your SQL Server running like a well-oiled machine!