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

New Cumulative Updates for SQL Server 2012, 2014, and 2016

6 years ago
Brent Ozar
SQL Server 2012, SQL Server 2014, SQL Server 2016, Updates
1 Comment

Good evening, and how are you doing tonight? Welcome to Café Updaté.

Tonight, Chef has prepared a delicious menu from the latest, freshest market ingredients. I’ll be back in a few moments to take your drink orders and tell you about the specials, but in the meantime, get comfortable, enjoy a glass of champagne, and take in the menu. There’s a lot to see here. Welcome!

SQL Server 2012 SP3 Cumulative Update 10

For dessert, a small 5-part sampler plate:

  • Access violation when you update compressed data
  • Timeout when you back up a large database to URL
  • Dimension security ignored by Power BI Desktop
  • CLR strict security added with trace flag 6545
  • Change Data Capture stopped working after a cumulative update

SQL Server 2014 SP2 CU6 and SP1 CU13

A delightful tasting menu of changes including the things in 2012 SP3 CU10, plus:

  • Log backup failure in AG secondaries
  • Access violation when you create an index with page compression
  • Failed to resume an AG secondary after a write failure
  • Access violation when you query a clustered columnstore when the data pages are too far apart (God bless that KB author for their honesty)
  • Unable to rebuild a partition online if it had a computed partitioning column
  • Stored procedure may fail after automatic failover
  • Assertion occurs when you run queries with a MERGE JOIN
  • Access violation if a stored proc is dropped before executing END TRY
  • UNION ALL with row goals runs slower in 2014 compared to 2008R2
  • CHECKFILEGROUP reports false inconsistency error on partitioned tables
  • Non-yielding scheduler during spinlock contention

SQL Server 2016 SP1 CU4 and RTM CU

And finally, for our main course, all of the above updates plus gems like:

  • Catch of the Day: Parallel queries return incorrect results for merge joins
  • Data mask on a floating points column is removed unexpectedly
  • Assertion failure when backing up large TDE encrypted databases
  • Deadlocks in SSISDB when you run multiple packages at once
  • Analysis Services caches stale data
  • Deadlocks in DMVs when performing large DDL operations
  • Non-yielding scheduler when you change the bucket_count for large memory-optimized tables
  • Access violation when you update partitioned tables with persisted computed columns
  • SUSER_SNAME function returns different results between 2014 & 2016
  • Can’t truncate partitions if they have extended or XML indexes
  • dm_db_incremental_stats_properties doesn’t show all partitions
  • Access violation if you run a non-distinct aggregate over a string column in a clustered columnstore table
  • Server stops responding when the latch_suspend_end XE is incorrectly triggered
  • Assertion on a secondary when you resume a suspended AG
  • AG databases not synchronizing after automatic failovers
  • Memory leak with in-memory OLTP
  • Restore fails for backups that combine compression, checksums, and TDE

I believe you’ll find something for everyone on tonight’s menu.

Here’s the best part: all of these updates will automatically be delivered to your hungry SQL Servers with absolutely no database administrators required whatsoever. Here at Café Updaté, our meals prepare themselves and –

wait –

I apologize, my assistant just informed me that our robotic automation is 86’d tonight. I’m sorry, but this means you’ll be applying these updates manually.

We’re setting up for your first hotfix

To all of your SQL Servers.

Just like you always have.

I’m sure that’s only a momentary issue, though. If you visit us tomorrow night, we might have made some progress on that unfortunate issue.

I’ll be back in a few moments with the grapes so you can start making your own wine.

Brent Ozarhttp://sqlserverupdates.com
I make Microsoft SQL Server faster and more reliable. I love teaching, travel, and laughing.
Previous Post
SQL Server 2014 Updates: SP2 CU5, SP1 CU12
Next Post
New Service Pack 4 for SQL Server 2012

1 Comment. Leave new

  • Solomon Rutzky
    February 27, 2018 10:29 pm

    Good news: documentation is now available for new Trace Flag 6545 (noted above under SQL Server 2012 CU changes, but is actually available in all updates, across all three versions, listed here). Please see the following post for the documentation detailing this new trace flag:

    https://SqlQuantumLeap.com/2018/02/23/sqlclr-vs-sql-server-2012-2014-2016-part-7-clr-strict-security-the-problem-continues-in-the-past-wait-what/

    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