Microsoft has released SQL Server 2012 Service Pack 2 Cumulative Update 8, which is Build 11.0.5634.1. This CU has 23 fixes in the public fix list, and a number of them look pretty significant. If you are on SQL Server 2012, you need to be on the Service Pack 2 branch by now (especially since the RTM and SP1 branches are no longer “supported service packs”). If you are on SP2, I think you are much better off on the latest cumulative update than on the original SP2 RTM build.
All Good Things Must Come to an End
All good things must come to an end. After slightly over seven and a half great years at SQLskills, it is time for me to
8 thoughts on “SQL Server 2012 SP2 Cumulative Update 8 Available”
Glenn,
Any ideas about KB3088480 on data spill for large sorts? What can trace flag 7470 do?
Thanks
Chris
Nope. We have a question in to Microsoft about that.
I will be very interested to hear what they say.
From the premium Support article:-
Note After applying this hotfix, enable trace flag 7470 to make SQL server consider internal data management memory overhead when calculated required memory for sort. This will increase memory requirement for sort queries and avoid spills in the situation explained in the Symptoms section above. Note this may impact memory availability for concurrent queries, therefore it is recommended to use the trace flag selectively.
Chris
That description is a little better, but a couple of us are pressing Microsoft for more detailed information.
The KB article is up to Revision 3 dated yesterday with no noticeable difference.
Chris
DO you know an approximate to install CU8 or CU9? Not looking for an exact but something I can give to the exec for a downtime. If averages an hour, good if it averages 4 hour ok as well. I just do not want to say 1 hour and it takes 3 every time.
thanks
mike
SQL Server 2012 Cumulative Updates typically take about 5-10 minutes to install, depending on the speed of your system. Certainly not 3-4 hours! Most of the time, a reboot of the server is not required. Making sure that SSMS is not running locally during the installation will minimize the chances of needing a reboot.