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 Cumulative Update 2

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

A-one, and a-two – here’s Cumulative Update 2, or as they say in Mexico, DOS. The fix list is pretty long, and here’s some of the greatest hits:

  • DML statements unexpectedly replicated to subscribers
  • Query returns incorrect results from nonclustered columnstore index
  • Incorrect results are returned when query contains a GROUP BY
  • Standard Edition’s Analysis Services ignores the 16GB memory limit
  • Query Store returns unusual characters (like Erik Darling) when a JOIN operator is used
  • Retention policy doesn’t work when you use Managed Backup to Azure
  • Updating while compression is in progress can lead to nonclustered columnstore index corruption
  • Access violation occurs when you use TDE and BPE
  • Queries that run against Always On Availability Group secondaries always get recompiled
  • Memory leak occurs when you use Azure Storage
  • Access violation occurs when query contains many COUNT DISTINCT operations
  • Access violation occurs if trace flag 4139 is enabled
  • High CPU usage after you install SQL Server
  • SQL Server doesn’t start after you configure TempDB to use a very small log file
  • Access violation on secondary replica when there are too many parallel redo operations
  • Query runs slowly when SQL Server uses a hash aggregate in the plan

And many, many more. Go check it out.

Brent Ozarhttp://sqlserverupdates.com
I make Microsoft SQL Server faster and more reliable. I love teaching, travel, and laughing.
Previous Post
Announcing SQL Server 2012 SP3 CU5
Next Post
SQL Server 2014 SP2 CU2 Released

4 Comments. Leave new

  • Chris C
    September 22, 2016 2:23 pm

    This seems like a dumb fix…”Standard Edition’s Analysis Services ignores the 16GB memory limit” … yes MS please take away memory that was forgotten to be locked down.

    Reply
    • Brent Ozar
      September 22, 2016 4:39 pm

      I wondered how many people were going to catch that, hahaha.

      Reply
  • Mike
    September 22, 2016 4:32 pm

    Why Microsoft puts artificial memory limits on any of their SQL Server products is at best questionable. It’s even worse, however, when Microsoft has to put a “fix” in place to bring the Standard Edition of Analysis Service (tabular mode) back down to their artificial 16GB memory limit. Should have left it alone. Was better before the “fix.”

    Reply
  • Jeff
    September 23, 2016 2:54 pm

    It doesn’t seem like the link to the update is working. Did Microsoft pull it back?

    https://support.microsoft.com/en-us/kb/3182270

    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