Microsoft just dropped Cumulative Update 27 for SQL Server 2019.
It includes a bunch of fixes for Availability Groups and for Change Tracking, interestingly, even if you aren’t using Change Tracking you might be affected. Happy patchin’!
Announcing SQL Server 2019 CU27
Brent Ozarhttps://sqlserverupdates.com
I make Microsoft SQL Server faster and more reliable. I love teaching, travel, and laughing.
Previous Post
Announcing SQL Server 2019 CU21, 2022 CU5
Next Post
Security Update to Avoid Remote Code Execution
Subscribe
Want to get an email when Microsoft publishes a new SP or CU for SQL Server? Subscribe here.
Recent Updates
- New Security Updates to Fix SQL Injection Vulnerabilities August 13, 2025
- A Bunch of Security Updates for 2016-2022 Just Dropped. July 9, 2025
- New Security Patches for SQL Server 2022, 2019, 2017, and 2016 October 8, 2024
- Announcing SQL Server 2022 CU14 July 23, 2024
- Security Update to Avoid Remote Code Execution July 10, 2024
2 Comments. Leave new
Hey Brent’s back on this site! 😀
My friend says: note that known issue #1 equates to 10GB of error logs per day in their environment. So check your error logs and watch your drive space! Released on June 13th, no fix yet. Tick, tick, tick…
From the CU KB page:
“Known issues in this update
Issue one: Excessive logging of asynchronous API call warning in the error log
The newly-created warning message in issue 2901635 might fill up the SQL Server error log with thousands of occurrences. The message is “WARNING Long asynchronous API Call: The scheduling fairness of scheduler can be impacted by an asynchronous API invocation unexpectedly exceeding xxx ms.” This is due to an incorrect code change during the build process. If you experience this issue and prefer not to uninstall the CU as a solution, contact Microsoft Support.
Microsoft is working on a fix for this issue and it will be available in a future CU.”