Posts by DBA Services

**Title: SQL Server Security Updates: The Saga Continues!**

Gather ’round, SQL Server aficionados, because Microsoft has just dropped a fresh batch of security patches for SQL Server 2022, 2019, 2017, and 2016! It’s like Christmas came early for database administrators everywhere. 🎄✨

Now, before you start popping the champagne, let’s dive into what these updates are all about. Microsoft has released a series of GDR security updates, and you can find all the juicy details in their [security advisory](https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2024-37341).

But here’s the kicker: these updates aren’t introducing any groundbreaking security fixes. Instead, they’re here to clean up the mess left behind by the last round of patches. Remember those pesky functional bugs in Change Data Capture (CDC) from the September update? Well, Microsoft heard your cries and decided to give those bugs the boot. It’s like a software spring cleaning, and who doesn’t love a tidy database?

For those of you who love the nitty-gritty details, you can check out the [description of the security update for SQL Server 2022 CU14](https://support.microsoft.com/en-us/topic/kb5042578-description-of-the-security-update-for-sql-server-2022-cu14-september-10-2024-560e6e4c-1f49-4c18-9eb7-054e9fdee3c7#known). It’s a riveting read, I promise.

Now, if you’re sitting there thinking, “But what about new security vulnerabilities?” Fear not, dear reader. This update is all about refining and perfecting the previous patches. It’s like upgrading from a regular coffee to a double-shot espresso – same great taste, just a little more kick.

As always, if you have any insider info or just want to share your thoughts on these updates, drop a comment below. Let’s get the conversation going!

And for those who want to stay on top of all things SQL Server, make sure to bookmark [SQL Server Builds](https://sqlserverbuilds.blogspot.com/) for the latest and greatest in update news.

Until next time, happy patching! 🛠️

# SQL Server 2022 CU14: The Update You Didn’t Know You Needed!

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 guess what? Your journey just got a little more exciting. Buckle up, because Cumulative Update 14 (CU14) 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 Swiss Army knife for your SQL Server, addressing a variety of issues that could make your life a whole lot easier. Here’s a sneak peek at what’s inside:

### 1. VSS Backups: The Ghost of Databases Past
Ever had VSS backups fail because you deleted a database? It’s like your server is haunted by the ghosts of databases past. Well, CU14 is here to exorcise those spirits and ensure your backups run smoothly.

### 2. The SQL Server Launchpad: The Service That Never Sleeps
Imagine a service that just won’t shut down, no matter how nicely you ask. That’s been the SQL Server Launchpad for some users. With CU14, you can finally put this insomniac service to bed.

### 3. Availability Groups: The Synchronization Mirage
You’ve just executed a “successful” failover, but your Availability Groups replicas are showing “Not Synchronizing” for several minutes. It’s like a cruel mirage in the desert of database management. CU14 brings the oasis, fixing this pesky issue.

### 4. Linux Memory Limits: The Ignored Boundaries
Running SQL Server on Linux? You might have noticed it sometimes ignores memory limits, like a rebellious teenager. CU14 steps in as the responsible adult, ensuring your server respects the boundaries you set.

### 5. Plan Cache Leaks: The Sneaky Culprits
Plan cache leaks and access violations due to Cardinality Estimation feedback race conditions can be as sneaky as ninjas in the night. CU14 shines a spotlight on these culprits, fixing the leaks and violations.

### 6. Change Tracking Auto Cleanup: The CPU Burner
Even when Change Tracking (CT) isn’t enabled, auto cleanup can burn through your CPU like there’s no tomorrow. CU14 puts an end to this unnecessary resource hogging, giving your CPU a much-needed break.

## Why You Should Update

This update is looking like a must-apply for anyone running SQL Server 2022. With fixes that address critical issues, CU14 is set to make your SQL Server experience smoother and more reliable. So, what are you waiting for? Go get ’em!

For more details on this update, check out the official [Microsoft update page](https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate14). If you need a broader overview of SQL Server builds, head over to [SQLServerBuilds](https://sqlserverbuilds.blogspot.com/).

Happy updating, and may your databases be ever in your favor!

# 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](https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate14) 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](https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate14) 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](https://sqlserverbuilds.blogspot.com/).

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

# Stay Safe: New Security Updates for SQL Server 2022, 2019, and 2017

Hey there, SQL Server aficionados! 🚀

We’ve got some hot-off-the-press news from the tech world that you won’t want to miss. Microsoft has just rolled out a series of crucial GDR (General Distribution Release) updates for SQL Server 2022, 2019, and 2017. And trust me, this is one update you’ll want to prioritize.

## Why Should You Care?

Imagine this: you’re sipping your morning coffee, blissfully unaware that a nefarious hacker is trying to exploit a vulnerability in your SQL Server connection driver. Scary, right? Well, that’s exactly the kind of nightmare scenario these updates aim to prevent.

The issue at hand is a security flaw that could allow bad actors to infiltrate a connection driver. Once that compromised driver connects to SQL Server, it could trigger arbitrary code execution on the client side. In layman’s terms, it’s like giving a stranger the keys to your house and hoping they don’t throw a wild party.

## What’s in the Update?

These GDR updates are designed to patch this vulnerability, ensuring that your SQL Server environment remains secure and your data stays safe. Whether you’re running SQL Server 2022, 2019, or 2017, there’s an update tailored just for you.

## How to Get the Update

Ready to fortify your defenses? Head over to the official Microsoft update page or check out [SQL Server Builds](https://sqlserverbuilds.blogspot.com/) for the latest links to these essential GDRs.

## Final Thoughts

In the ever-evolving landscape of cybersecurity, staying one step ahead is crucial. These updates are a testament to Microsoft’s commitment to keeping your data secure. So, don’t delay—update your SQL Server today and sleep a little easier tonight.

Stay safe, stay updated, and happy querying! 🌐🔒

For more details and to grab the updates, visit the [Microsoft update page](https://sqlserverbuilds.blogspot.com/).

—

Feel free to share your thoughts or any questions in the comments below. Let’s keep the conversation going!

# Shield Your SQL Server: New Security Updates to Thwart Remote Code Execution

Hey there, SQL Server aficionados! Gather ’round because we’ve got some crucial news straight from the tech trenches. Microsoft has just rolled out a series of GDR (General Distribution Release) updates for SQL Server 2022, 2019, and 2017. And trust me, you don’t want to miss this one.

## The Threat: Remote Code Execution

Imagine this: a nefarious hacker manages to sneak into your connection driver. Once that driver connects to your SQL Server, boom! They could execute arbitrary code on your client. Sounds like a plot straight out of a cyber-thriller, right? Unfortunately, it’s a very real threat. But fear not, because Microsoft has swooped in to save the day.

## The Solution: GDR Updates

These new GDR updates are designed to patch up the security loophole that could allow such a dastardly deed. By installing these updates, you’re essentially putting up a digital fortress around your SQL Server, ensuring that bad actors can’t exploit this vulnerability.

## How to Get the Updates

Ready to fortify your defenses? Head over to the official Microsoft update page for the specific GDRs for SQL Server 2022, 2019, and 2017. If you need a more general overview, you can also check out [SQL Server Builds](https://sqlserverbuilds.blogspot.com/).

## Stay Updated, Stay Safe

Keeping your SQL Server up-to-date is not just a good practice; it’s essential for maintaining the security and integrity of your data. So, don’t delay—apply these updates and keep those cyber-villains at bay.

For more detailed information and direct links to the updates, you can visit the [Most Recent Updates page](https://sqlserverbuilds.blogspot.com/).

Stay safe, stay updated, and happy querying!

—

For the original announcement, check out the [Security Update to Avoid Remote Code Execution](https://sqlserverbuilds.blogspot.com/news/security-update-to-avoid-remote-code-execution/).

# Exciting News: SQL Server 2019 CU27 is Here!

Hey there, SQL Server enthusiasts! Buckle up because Microsoft has just unleashed the latest and greatest update for SQL Server 2019: Cumulative Update 27 (CU27). This isn’t just any ordinary update—it’s packed with a slew of fixes and enhancements that are sure to make your SQL Server experience smoother and more efficient.

## What’s New in CU27?

### Availability Groups Fixes
First up, let’s talk about Availability Groups. If you’re running a high-availability environment, you’ll be thrilled to know that CU27 includes several crucial fixes. These updates aim to enhance the stability and performance of your Availability Groups, ensuring that your data remains accessible and your systems stay resilient.

### Change Tracking Fixes
Now, here’s something interesting: CU27 also brings a host of fixes for Change Tracking. Even if you’re not actively using Change Tracking, these updates could still impact you. That’s right—Microsoft has fine-tuned various aspects of SQL Server to ensure that even dormant features don’t cause unexpected issues.

## Why Should You Care?

You might be wondering, “Why should I bother updating if I’m not using these specific features?” Well, the beauty of cumulative updates is that they often include a variety of improvements that can benefit your system as a whole. From performance enhancements to security patches, there’s always something valuable in these updates.

## Ready to Update?

If you’re ready to dive into CU27, you can find all the details and download links on the official [Microsoft update page](https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2019/cumulativeupdate27). For a broader overview of SQL Server builds, you can also check out [SQL Server Builds](https://sqlserverbuilds.blogspot.com/).

## Happy Patching!

So, what are you waiting for? Get your systems updated and enjoy the latest improvements that SQL Server 2019 CU27 has to offer. Happy patching, and may your databases run smoother than ever!

Stay tuned for more updates and happy querying!

# Exciting News: SQL Server 2019 CU21 and 2022 CU5 Are Here!

Hold onto your keyboards, SQL Server enthusiasts! Microsoft has just dropped some major updates that are sure to make your data-driven hearts skip a beat. Say hello to **SQL Server 2019 CU21** and **SQL Server 2022 CU5**! (Sorry, SQL Server 2017 fans, no love for you this time around.)

## What’s New in SQL Server 2019 CU21?

First up, let’s dive into the treasure trove of updates in SQL Server 2019 CU21. This cumulative update is packed with fixes and improvements, but let’s start with a couple of known issues that you might want to keep an eye on:

### Known Issues

1. **SESSION_CONTEXT Shenanigans**: If you’re using `SESSION_CONTEXT`, you might encounter incorrect results with parallel plans. The fix introduced in CU14 has a side effect of creating access violation dump files. The workaround? Use trace flags 9432 to disable the CU14 fix and 11042 to disable parallelism when using `SESSION_CONTEXT`. Microsoft is working on a more permanent fix for a future CU.

2. **Managed Instance Link Mayhem**: If you’re using Managed Instance Link with memory-optimized tables, FileStream, or multiple log files, your database might stop syncing. The fix for this is a bit complex, so it’s best to check out the [CU21 page](https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2019/cumulativeupdate21#known-issues-in-this-update) for detailed instructions.

### Fixes and Improvements

Now, let’s get to the good stuff! Here are some of the key fixes and improvements in SQL Server 2019 CU21:

– **In-Memory OLTP Fixes**: A plethora of issues around In-Memory OLTP have been addressed.
– **Query Fixes**:
– Incorrect results for queries filtering on `ROW_NUMBER` with nullable columns? Fixed!
– Errors and access violations with multiple occurrences of the same scalar subquery? Gone!
– Improved cardinality estimation for `AND` predicates.
– Inconsistent results caused by a parallel spool in plans for `INSERT`, `UPDATE`, or `DELETE` queries? No more!
– Enhanced change tracking cleanup queries when using trace flags 8286 and 8287.

For the full list of fixes and improvements, head over to the [official update page](https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2019/cumulativeupdate21).

## What’s New in SQL Server 2022 CU5?

Not to be outdone, SQL Server 2022 CU5 also brings a host of exciting updates and fixes. Here’s a sneak peek at some of the highlights:

– **In-Memory OLTP Fixes**: Just like its 2019 counterpart, SQL Server 2022 CU5 addresses several issues around In-Memory OLTP.
– **Memory Leak Fix**: Running queries with an equals (`=`) predicate on a clustered columnstore index? Say goodbye to memory leaks!
– **Race Condition Fix**: Parameter-sensitive plan optimization with Query Store turned on? No more race conditions!
– **Index Fix**: Incorrect results with indexes that have a `DESC` sort order? Fixed!

For more details, check out the [official update page](https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate5).

## Ready to Update?

These updates are packed with fixes and improvements that can make your SQL Server experience smoother and more efficient. So, what are you waiting for? Dive into the latest cumulative updates and take your SQL Server game to the next level!

For a comprehensive list of all SQL Server builds, you can always visit [SQL Server Builds](https://sqlserverbuilds.blogspot.com/).

Happy updating, and may your queries always be swift and your data always be accurate!

Are you wanting to fine-tune your data management services? Optimizing SQL Server performance is crucial for ensuring that your applications run smoothly and efficiently. Whether you’re managing complex queries or simply trying to improve response times, performance tuning is a skill that every developer should master. This article from the Microsoft Certified experts at DBA…

# SQL Server 2022 Gets Its 2nd Update in 2 Days: A Rollercoaster of Fixes and Features!

Hold onto your keyboards, folks! Just when you thought it was safe to take a breather, Microsoft has dropped another bombshell. On Tuesday, we were graced with a General Distribution Release (GDR), and today, we’re hit with [Cumulative Update 1](https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate1). It seems like Microsoft is making up for lost time, and we’re here for the ride!

## What’s New in Cumulative Update 1?

This update is packed with a plethora of fixes and improvements that will make your SQL Server 2022 experience smoother than ever. Here are some of the highlights:

### 1. Differential Backup Fix
Ever had your differential backup skip new Page Free Space (PFS) pages after a data file grows around a PFS boundary? Yeah, that’s a mouthful. But more importantly, it could lead to database corruption and a possible crash dump when restoring the differential backup. This update fixes that pesky issue, so you can sleep a little easier.

### 2. Hybrid Buffer Pool with Direct Write
Previously, you needed to enable trace flag (TF) 809 to use the hybrid buffer pool with the direct write feature. Not anymore! This update removes that requirement, and the feature is now enabled by default in SQL Server 2022. Less hassle, more efficiency!

### 3. Azure SQL Database Improvement
The `sp_invoke_external_rest_endpoint` stored procedure is now only supported in Azure SQL Database environments. This improvement ensures that your SQL Server is optimized for the cloud.

### 4. Read Query Fix on Readable Secondary Replica
If you’ve ever had a read query on a readable secondary replica get aborted or return unexpected results due to heap and forwarding records, this update has your back. No more unexpected surprises!

### 5. Access Violation Fix
An access violation could occur when temporary tables are invoked inside User-Defined Functions (UDFs) using synonyms. This issue has been addressed in both SQL Server 2022 CU1 and SQL Server 2019 CU19.

### 6. Security Fix
An authenticated attacker could affect SQL Server memory by executing a specially crafted CREATE STATISTICS or UPDATE STATISTICS statement. This update fixes that vulnerability, keeping your server secure.

### 7. Memory Leak Fix
A gradual memory leak in the SQL Server process caused by the Log Reader Agent in transactional replication has been fixed. Say goodbye to high memory usage under MEMORYCLERK_SOSNODE!

### 8. Safeguard for Memory Capacity Issues
This fix acts as a safeguard for issues that can cause unavailability due to memory capacity in some rare queries, particularly nested queries performing table scans.

### 9. Database Accessibility Fix
High-volume customer workloads using Extensible Key Management (EKM) for encryption and key generation were facing database accessibility issues. This update addresses those problems, ensuring smooth operations.

### 10. CEIP Telemetry
The update adds the queries and category of the Microsoft Customer Experience Improvement Program (CEIP) telemetry to SQL Server 2022. More data for better improvements!

## And There’s More!
These are just the highlights. For the full list of fixes and improvements, check out the [official update page](https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate1).

So, what are you waiting for? Go get that update! And while it’s unlikely we’ll see another update tomorrow, who knows what surprises Microsoft has in store for us next? Stay tuned, and keep your servers running smoothly!

For more information on SQL Server builds, visit [SQL Server Builds](https://sqlserverbuilds.blogspot.com/).