The SQL Server team has released SQL Server 2012 SP2 Cumulative Update #1. This cumulative updates Service Pack 2 to include the fixes from SP1 CU#10 and a few from CU#11, including the fix for the online index rebuild corruption issue I discussed recently on SQLPerformance.com. It also marks the first time in the SQL Server 2012 timeframe that both cumulative update branches are on roughly the same schedule, which makes many of us happy I'm sure. 🙂
- KB Article: KB #2976982
- Build # is 11.0.5532
- Currently there are 45 public fixes listed (46 total)
Relevant for builds 11.0.5058 -> 11.0.5531. Do not attempt to install on SQL Server 2012 RTM (any build < 11.0.3000) or SP1 (any build < 11.0.5058), or any other major version. If you are on a different branch, see this blog post for information on the latest fixes for RTM and Service Pack 1.
That database would be very helpful for situations like Paul White just detailed about found in SQL2008R2 SP2 CU11. See http://sqlperformance.com/2014/07/sql-lock-block-deadlock/2008-r2-bug-fix-breaks-rcsi
Thanks to his research he discovered that it is fixed differently in SQL2012 SP1 and SQL2012 SP2 and is not an issue in SQL2014.
Chris
Yes, an online database containing the bugfixes with the option to search for specific fixes (for example: give me all the fixes for mirroring after SP1) is on my wishlist too. I've copied several parts of the kb articles in excel, but that's a pain ********
Right now, it's almost impossible to search for fixes without taking a day off…
Aaron,
Looks like SP2 branch might be playing catch-up with SP1 fixes coming one month and the SP2 versions the following month.
Hope not.
Chris
Thanks for clearing that up and Yes, that would be sweet if such a database existed.
@Kevin sorry, I've made that more clear. It's not *all* of the fixes from CU#11, probably just due to timing issues. A couple of examples that appear in both:
http://support.microsoft.com/kb/2975402
http://support.microsoft.com/kb/2974948
http://support.microsoft.com/kb/2969896 (obviously)
Wouldn't it be great if there were a database that listed all of the KBs and cross-referenced them to show when they appeared in which branch – and if they don't currently appear in a branch, why not? That branch was out of support? That branch was never affected by the bug (e.g. a regression)? The fix is forthcoming?
Does SQL Server 2012 SP2 CU1 really have SQL Server 2012 SP1 CU11 fixes in it?
This Blog entry just says it has SP1 CU10 fixes.
http://blogs.msdn.com/b/sqlreleaseservices/archive/2014/07/23/cumulative-update-1-for-sql-server-2012-sp2.aspx
@tobi yes, security issues are probably a common one that they don't document publicly because it jeopardizes the people who don't or can't patch. I'm sure there are other cases too, like minor issues that were never observed outside of Redmond. I never know the exact nature of the "missing" fixes, I just know the counts.
What's with the non-public fix? A security issue?