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 2016 SP2 CU6: The Update You’ll Remember Forever

4 years ago
Brent Ozar
SQL Server 2016, Updates
8 Comments

I’ll always remember where I was on Tuesday, March 19th, 2019 at 6:55PM.

I was sitting in the Seattle airport, waiting to board the last leg of my flights home to San Diego. I happened to check my phone, and…

It was here.

The update we’d waited for for YEARS had finally landed. Yes, ladies and gentlemen, Microsoft fixed the “String or binary data would be truncated” error! It’s true! Be still, your beating hearts!

KB #4468101 tells you that if you enable trace flag 460, SQL Server will finally tell you just what in the sam hell is going to be truncated.

SP2 CU6 also includes a lot of other fixes like:

  • Users are incorrectly permitted to create incremental stats on nonclustered indexes that aren’t aligned to the base table
  • Assertion for parallel deletes from filestream tables
  • Filestream IO can’t be enabled on cluster shared volumes
  • Assertion for linked server queries that point to themselves during a cross-database transaction (talk about a perfect storm)
  • MDS database upgrade fails
  • Filtered nonclustered columnstore index over a clustered columnstore index may not be maintained (that’s an interesting term for corruption)
  • Stack dump during change tracking cleanup
  • Data masking doesn’t

Here’s the full list of fixes in SQL 2016 SP2 CU6, and also today, Microsoft dropped 2016 SP1 CU14. But screw that one – that one doesn’t have our sweet, sweet #4468101 fix. Go get you some of that.

Brent Ozarhttp://sqlserverupdates.com
I make Microsoft SQL Server faster and more reliable. I love teaching, travel, and laughing.
Previous Post
Announcing SQL Server 2014 SP3 CU2 and SP2 CU16
Next Post
Announcing SQL Server 2017 Cumulative Update 14

8 Comments. Leave new

  • Patrick Hurst
    March 20, 2019 2:50 am

    Noooooooooo! I listed the ability to correctly identify the string on my resume under special skills! I’m ruined.

    Reply
  • Tim Brown
    March 20, 2019 1:41 pm

    I think the biggest question here is why would they make this optional? Who would ever say
    “nope I like the old way better”

    Reply
    • Tim Cockerham
      March 20, 2019 2:03 pm

      Who? People that still have televisions with knobs to change the channels.

      Reply
      • Tim Brown
        March 20, 2019 2:15 pm

        Good point perhaps the same people who still use the pager option for Job Step Errors

        Reply
  • Brent Ozar
    March 20, 2019 2:28 pm

    The biggest reason it’s optional: anytime you change behavior in SQL Server, you can end up with bugs. Trace flag 460 has a bug described in this morning’s upcoming post: https://www.brentozar.com/archive/2019/03/how-to-fix-the-error-string-or-binary-data-would-be-truncated/

    Reply
  • K Hyer
    March 20, 2019 3:18 pm

    Why optional indeed!

    “Well, our code doesn’t really account for that response from the SQL Server..”
    -Every Dev Team Ever. 😉

    Reply
  • D Shroka
    May 15, 2019 1:56 pm

    Anyone have an issue with VSS backups after applying? We applied CU6 to 2 servers out of 4. Once applied we receive the below message and it sends the SQLServerWriter into Non-Retryable state until I restart the SQL VSS service. No error messages in the SQL logs, but also no longer seeing the I/O Freeze and I/O resumed messages just before the backup process. SSMS backups are working fine, and Azure shows snaps are fine.
    Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 102
    Error state: 1, Severity: 15
    Source: Microsoft SQL Server Native Client 11.0
    Error message: Incorrect syntax near ‘.’.

    Reply
    • Brent Ozar
      May 15, 2019 2:02 pm

      D – open a support call right away. There have been a lot of VSS bugs in the last several CUs, and I wouldn’t be surprised if you were hitting a new one. Don’t dilly-dally around with blog post comments – when your backups fail, call Microsoft, full stop.

      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 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
  • Announcing SQL Server 2019 CU13 and SSMS 18.10: Replication Improvements October 5, 2021

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