SQLServerUpdates.com
  • Home – Most Recent Updates
    • SQL Server 2022 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

Announcing SQL 2017 CU17, 2016 SP2 CU10

4 years ago
Brent Ozar
SQL Server 2016, SQL Server 2017, Updates
2 Comments

OK, let’s get the awkwardness out of the way first: SQL Server 2016 SP2 CU10 is actually a fixed version of CU9. If you watched the SP2 CU9 blog post, you’ll note that people started hitting weirdness with the CU9 version numbers right away, then Microsoft added a note to the KB article telling you to hold off on CU9, and now…the CU9 KB article page has vanished altogether.

I understand how it is. I’ve had weekends like that, weekends that went so poorly that I wanted to erase all memory of what I did. Unfortunately, there’s the Internet. The Internet never forgets. (That’s not true for the cloud though: the cloud forgets all the time.)

Anyhoo, CU9 is dead to Microsoft, and CU10 replaces it. Everything we said about CU9, that same stuff is fixed in CU10.

Moving on to SQL Server 2017 CU17 – which I’m sure is completely bug-free, and will not be removed from the Internet within 9 days of release. CU17 includes hotfixes like:

  • Peer-to-peer replication fails if the host name is not uppercase
  • Columnstore queries may return incorrect results
  • Columnstore queries may return incorrect results (no no, this one is different)
  • Columnstore queries may return incorrect results (look, you try building a database)
  • Unexpected results for SSAS tabular mode queries (no no, not incorrect results. Just unexpected. Like if you expected correct results, these results would be, uh, unexpected.)
  • Always On takes a smoke break when you do a cross-database transaction
  • Access violation when you do a hash in batch mode
  • Access violation when you do a hash in batch mode (look, stop blaming the messenger, maybe the first bugfix had a bug. You should be glad they caught it before it was released to you and pulled 9 days later, bucko.)
  • Non-yielding scheduler when you do a hash in batch mode (STOP LAUGHING, this is a different bug)
  • Non-yielding scheduler when you do a sort in batch mode
  • Restore of a compressed encrypted backup fails (remember, test your restores, people – a successful backup doesn’t mean diddly)

Hoowee. I’m not even listing all of the bug fixes! Go get it, and … maybe not apply it in production right away. Maybe put it into your development environment for a couple of weeks. If it breaks your development server, well…hey, you can always say it was a code problem.

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 CU9
Next Post
New SQL Server 2017 CU18 and 2016 SP2 CU11

2 Comments. Leave new

  • JM
    October 9, 2019 9:19 am

    Kudos for the light tone. By the time I got to “smoke break” I was literally LOLing.

    Reply
    • Brent Ozar
      October 9, 2019 9:23 am

      Thanks. We try to have a little fun around here. 😀

      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 CU21, 2022 CU5 June 15, 2023
  • SQL Server 2022 CU3: How Stella Got Her Groove Back April 13, 2023
  • 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

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