SQL 2016 SP2 CU6 is released also SQL 2016 SP1 CU 14

March 21st, 2019 by Stephen Jones Leave a reply »

The good news is that Microsoft has fixed the “String or binary data would be truncated” error!
With KB#4468101 if you enable trace flag 460, the SQL Server will now tell you just what l is going to be truncated.
SP2 CU6 also includes 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 (as bad as it sounds)
• MDS database upgrade fails
• Filtered nonclustered columnstore index over a clustered columnstore index may not be maintained ( in layman’s term we call it corruption)
• Stack dump during change tracking cleanup
• Data masking (doesn’t)

Microsoft also released an 2016 SP1 CU14 but that doesn’t have the key#4468101 fix. .

Advertisement

Comments are closed.