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

New SQL Server 2019 CU9, 2016 SP2 CU 16

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

Late last year, Microsoft announced that they were going to hold off on patches for a while due to the pandemic and the holidays.

Incorrect results bugs:

  • Incorrect query results from the CONCAT function
  • Incorrect results from in-memory optimized tables with clustered columnstore indexes (this one’s only got 2016 in the KB, not 2019 – it’s not clear whether 2019 was unaffected, or just not patched)
  • Incorrect results on linked server queries with aggregates or joins on a remote table with a filtered index
  • Incorrect results for inserting data into memory-optimized tables and UDFs
  • More fixes for inlined scalar functions – out of memory errors, access violations, and non-yielding scheduler errors. They didn’t add any new situations where they stop the function from inlining, though, so that’s good.
  • Incorrect data mask applied for queries with UDFs
  • Incorrect results between in-memory optimized tables and disk-based tables – no notes on this one, so guessing it’s super-rare or super-embarrassing or both

Other bugs:

  • If you have columnstore trace flags 876, 11064, and 11068 turned on, you may end up with single-row rowgroups
  • MERGE statement fails (OMG, they’re finally fixing bugs in the MERGE statement)
  • Rollback never finishes if there’s an XE session present for sql_transaction events
  • Severe spinlock contention – this one was also reported in 2019 CU8, so apparently more work has been done
  • Improves Query Store scalability for ad-hoc workloads
  • Memory leak when auditing is turned on

There are also a LOT of fixes for Availability Groups and external queries, like Big Data Clusters and querying Oracle.

Go get ’em! Here’s 2016 SP2 CU16 and 2019 CU9. It’s been 5 months since 2017 was updated, too, so I wouldn’t be surprised to see 2017 CU23 drop sometime soon.

Brent Ozarhttp://sqlserverupdates.com
I make Microsoft SQL Server faster and more reliable. I love teaching, travel, and laughing.
Previous Post
Extended Events Security Issue in SQL Server 2019, 2017, 2016, 2014
Next Post
Announcing SQL Server 2019 Cumulative Update 11: This One Goes to …

2 Comments. Leave new

  • Chris S.
    February 12, 2021 9:20 am

    I ain’t gonna “go get ’em” unless your pessimism about SQL Server 2019 updates has been assuaged by what you have seen from CU9. Awaiting your honest & brutal review of CU9 before I jump off a cliff without a parachute.

    Reply
  • Regi Vih
    March 1, 2021 8:56 am

    SQL Server 2019 CU9 includes GDR update (relased on 2021/01/12) or not?

    Thanks.

    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

  • 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
  • Announcing SQL Server 2017 Cumulative Update 25: The Silver Anniversary July 12, 2021
  • Announcing SQL Server 2019 Cumulative Update 11: This One Goes to … June 11, 2021

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