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

Announcing SQL Server 2017 Cumulative Update 7

5 years ago
Brent Ozar
SQL Server 2017, Updates
2 Comments

Cumulative Update 7 is out, just about one month after CU6. If you’re using Transparent Data Encryption or In-Memory OLTP, heads up:

  • Non-yielding scheduler when you try to recover an In-Memory OLTP database
  • Backups corrupted if you do a compressed backup on a database with TDE
  • Restore of a compressed backup of a TDE database fails

Because of those 3 fixes, I’d highly, highly recommend applying this CU as soon as practical if you’re using Transparent Data Encryption and/or In-Memory OLTP. I’ve lived through bugs that prevented me from doing a restore, and that’s something I wouldn’t wish on anybody.

The CU has a few other engine fixes, plus a whole lot of Analysis Services fixes:

  • Analysis Services totals are wrong after you filter, then remove the filter
  • Analysis Services memory exhaustion bugs (2)
  • Analysis Services error when you create a subcube (this shows how little I know about SSAS – I didn’t know there was such a thing as a “subcube,” and I’m now going to use that term for anyone’s undersized office cubicle)
  • A couple of SSAS crash errors, stops responding, access violation, etc
  • Added Transparent Data Encryption support for log shipping
  • Floating point overflow errors in in-memory OLTP

Head on over to check out the fix list.

Brent Ozarhttp://sqlserverupdates.com
I make Microsoft SQL Server faster and more reliable. I love teaching, travel, and laughing.
Previous Post
Announcing SQL Server 2016 Service Pack 2 (and this one is big!)
Next Post
SQL Server 2016 SP1 CU9: Sophie’s Cumulative Update

2 Comments. Leave new

  • RossW
    May 25, 2018 6:25 pm

    I am very concerned about the corrupt backups and TDE.
    “..but the restore will complete successfully with the CONTINUE_AFTER_ERROR option..”
    Did I understand the KB correctly, the corrupted backups are not really corrupt just reported as? I am going to try a test on Monday.

    Reply
  • RossW
    May 28, 2018 6:25 pm

    DB restore completed successfully, full and diff. Also our nightly verifyonly’s are completing successfully.

    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