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 2016 SP2 CU9

3 years ago
Brent Ozar
SQL Server 2016, Updates
3 Comments

Update 2019/10/02 – there is some confusion about the final build number. The KB article currently says 13.0.5470, the download page says 13.0.5479, and in the comments below, Edward says the download has some unsigned components. Might wanna hold off on this particular update for a few days.

Update 2019/10/08 – hold off on this update for now. The updated KB notes:

There is an uninstall issue with SQL16 SP2 CU9. The payload in CU9 is fine, but if you have not already installed CU9, it is recommended that you wait for the upcoming expedited SQL16 SP2 CU10 release.

Sixty days since the last 2016 Cumulative Update – love how reliable these are coming out – we’ve got Cumulative Update 9. Fixes include:

  • Transaction log isn’t truncated in a single-node AG
  • Access violation for PIVOT or UNPIVOT
  • Incorrect results with partitioned clustered columnstore indexes
  • Access violation when you restore an In-Memory OLTP database
  • Frozen IO won’t resume after backing up a database with In-Memory OLTP
  • Availability Groups direct seeding can’t stop, won’t stop
  • sys.database_scoped_configurations returns the wrong results (yay! The sp_Blitz check for non-default database scoped configs will finally work)
  • Better cardinality estimation

For those of you planning patch windows, it’s also been 60 days since the last 2017 CU, so that’ll likely drop this week too.

Brent Ozarhttp://sqlserverupdates.com
I make Microsoft SQL Server faster and more reliable. I love teaching, travel, and laughing.
Previous Post
SQL Server 2016 SP2 Cumulative Update 8
Next Post
Announcing SQL 2017 CU17, 2016 SP2 CU10

3 Comments. Leave new

  • Edward
    October 1, 2019 7:43 am

    just installed it, it failed, SQL started, and now i’m getting errors in the log like this:
    “Failed to verify the Authenticode signature of ‘C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\hkruntime.dll’. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.”
    So DON’T INSTALL IT. The build numbers are also wrong. The KB has 13.0.5470.0 but the download page (and SQL itself after updating) has 13.0.5479.0.

    Reply
  • Edward
    October 1, 2019 7:44 am

    forgot to mention, this is a genuine SQL!

    Reply
  • Andy
    October 7, 2019 2:20 pm

    Brent, I think the download link in your update is to CU8, not CU9.

    Also, the KB article page has been updated to correct the version mismatch Edward mentioned.
    Now says: “This article describes Cumulative Update package 9 (CU9) (build number: 13.0.5479.0)”

    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