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
2 Comments. Leave new
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.
DB restore completed successfully, full and diff. Also our nightly verifyonly’s are completing successfully.