SQLServerUpdates.com
  • Home – Most Recent Updates
    • SQL Server 2019 Updates
    • SQL Server 2017 Updates
    • SQL Server 2016 Updates
    • SQL Server 2014 Updates
    • SQL Server 2012 Updates
    • SQL Server 2008 R2 Updates
    • SQL Server 2008 Updates
  • Download SQL Server
  • Subscribe to Updates
  • Contact Us
    • Frequently Asked Questions

SQL Server 2019 Cumulative Update 5: A Box of Chocolates

3 years ago
Brent Ozar
SQL Server 2019, Updates
2 Comments

It’s here, and there seems to be a new style for posting the KB articles.

A lot of the bug fixes don’t have detailed KB articles, so they’re kinda like a box of chocolates.

Quick rundown of some of the issues:

  • “Fix:” Scalar UDF inlining issues – this KB article keeps getting expanded with each CU, but here’s the weird part: they’re not actually fixing the issues. They’re just disabling inlining in more queries. Hmm.
  • Fix: blocking may occur when Reduce Recompilations feature is enabled by default – I’ve tried wrapping my head around that title a few times
  • Improvement: TDE backup encryption setting changes – changes like this are a good reminder of why you gotta read every KB article now when you’re doing upgrades, because you might just have work to do even if you weren’t expecting it. Now you need to take a gander at your backup settings.
  • Corruption caused by shrinking a database – boy, they worked really hard to avoid using the word corruption here: “When shrinking a database, you may receive a database consistency error if the shrinking process encounters an IAM page that is the first and only IAM page. The symptoms may include assertions errors involving heapdataset. Confirm that you do not have any inconsistencies by executing DBCC CHECKDB after shrink operations. Applying this update will prevent future occurrence of this issue and not clean up past inconsistencies.”
  • Accelerated Database Recovery is not supported for databases using mirroring – I really liked the sound of ADR when it came out, but there have been some head-shaking bugs in this one.

I’m gonna be honest with you, dear reader: the lack of documentation on a lot of bugs in this KB – especially severe-sounding bugs, like the one about DELETEs getting false warnings about foreign key violations – I would probably hold off on this KB for a week or two and see if the community sounds an alarm about problems.

I’m usually a big fan of putting these updates on dev/QA/staging servers as quickly as practical to start sniffing out how it goes, but there’s something about this new mostly-undocumented release style that makes me nervous. But then again, I’m not a smart man.

Brent Ozarhttp://sqlserverupdates.com
I make Microsoft SQL Server faster and more reliable. I love teaching, travel, and laughing.
Previous Post
Unveiling SQL Server 2017 Cumulative Update 20: China
Next Post
SQL Server 2019 Cumulative Update 6: The CU6th Sense

2 Comments. Leave new

  • willem
    June 23, 2020 9:36 am

    Don’t be nervous Brent, they said you’ll have to cut the red wire. I’ll await outside the blastarea if you don’t mind.

    Reply
  • Paul-Sebastian Manole
    June 29, 2020 3:34 am

    And after building up all that hype around this version… talk about going flacid… 😅

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.

Subscribe

Want to get an email when Microsoft publishes a new SP or CU for SQL Server? Subscribe here.

Recent Updates

  • SQL Server 2022 Gets Its 2nd Update in 2 Days February 16, 2023
  • SQL Server 2022 Gets Its First Update! Plus 2019, 2017, 2016, 2014 Updates February 14, 2023
  • Announcing SQL Server 2019 CU15 January 27, 2022
  • Announcing SQL Server 2019 CU13 and SSMS 18.10: Replication Improvements October 5, 2021
  • Announcing 2016 Service Pack 3 and 2017 CU26 September 15, 2021

© 2021 Brent Ozar Unlimited®. All Rights Reserved. Privacy Policy