In April and May, Microsoft released cumulative updates for SQL Server 2008 and 2008 R2 (I blogged about them here and here). They are:
| Branch | Original CU | Build # | KB Article | Date Added |
|---|---|---|---|---|
| SQL Server 2008 SP3 | CU #11 | 10.00.5840 | KB #2834048 | 2013-05-20 |
| SQL Server 2008 R2 SP1 | CU #12 | 10.50.2874 | KB #2828727 | 2013-04-15 |
| SQL Server 2008 R2 SP2 | CU #6 | 10.50.4279 | KB #2830140 | 2013-04-15 |
Sometime after that, looks like the next day, both downloads were pulled, allegedly due to an index corruption issue (if you believe the commentary on the Release Services blog post for CU #6) or due to an issue with w3wp.exe (if you believe the label on the hotfix posted directly to the CU #6 article itself). Or perhaps both. At the very least you may see a regression involving index corruption or massive index size deviation when you rebuild a clustered index online and the plan involves a non-clustered index. I don't have a repro handy.
On June 13th, both articles were updated with new versions of the cumulative updates that no longer exhibit this symptom (sound familiar?). And they were updated again June 17th. So if you download today, you'll actually get:
| Branch | Updated CU | New Build # | KB Article | Date Updated |
|---|---|---|---|---|
| SQL Server 2008 SP3 | CU #11 | 10.00.5841 | KB #2834048 | 2013-06-17 |
| SQL Server 2008 R2 SP1 | CU #12 | 10.50.2875 | KB #2828727 | 2013-06-17 |
| SQL Server 2008 R2 SP2 | CU #6 | 10.50.4285 | KB #2830140 | 2013-06-17 |
Please check @@VERSION. If it reports 10.00.5840, 10.50.2874 or 10.50.4279, please go re-download and re-apply the relevant cumulative update for your branch. Better yet, if you're on 2008 R2, please see my post where I announce new CUs for the 2008 R2 branches:
| Branch | CU | Build # | KB Article | Date Added |
|---|---|---|---|---|
| SQL Server 2008 R2 SP1 | CU #13 | 10.50.2876 | KB #2855792 | 2013-06-17 |
| SQL Server 2008 R2 SP2 | CU #7 | 10.50.4286 | KB #2844090 | 2013-06-17 |
In cases like this, I really, really, really wish they would release a new, out-of-band cumulative update (this is a non-issue, now, for R2, but remains an issue for 2008 SP3 customers for another month or so). How many people go back and take another look at the CU article once they have downloaded, installed, and regression tested? Does everyone regression test a full set of online rebuilds, an operation that probably doesn't occur that often? I think many users will simply not see this update and are on the verge of experiencing the symptom – there simply isn't enough visibility when they quietly swap out the versions that the download links yield.
This situation still seems to be in some flux, at least for SQL Server 2008 R2.
The build list KB: "The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released" (http://support.microsoft.com/kb/2730301) currently shows 10.5.4279 for CU6 and 10.5.4286 for CU7.
The build list KB: "The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released" (http://support.microsoft.com/kb/2567616) currently shows 10.5.2874 for CU12 and 10.5.2876 for CU13.
It could be that Microsoft has not updated these build list KBs yet, or maybe they are not going to update them.
Thanks Glenn, I guess the new CUs got released just in time (though 2008 users are still kind of on their own). I suspect they'll update those KBs when the dust has settled.
They just released (30th August) the CU8 (http://support.microsoft.com/kb/2871401)
Once you need to give them your email to request the download couldn't they just email you an alert if you should download a new version? I agree with Aaron few people will recheck the old KBs to see if there were any update on the binaries.
This blog http://sqlserverbuilds.blogspot.in/ can help us to check any updates there was where I first knew about this issue with CU6.
Thanks Antonio, the CU was actually released a week earlier, but they must have made some modification to the content on the 30th.
I blogged about it on August 23:
https://sqlblog.org/blogs/aaron_bertrand/archive/2013/08/23/august-2013-cumulative-updates-for-sql-server-2008-r2.aspx
I have installed the SP3, however in between I have received one issue as NTservice could not start. Not sure the reason but the NW team was working some port changes. When I tried to start the SQL it did not and was asking for some resourcefile not available. Then I tried copying that file from UAT env and could able to start the SQL. But when I tried to login, I got message like "DB is in script upgrade mode, Only administrator can login". Without any option I had uninstalled it. Then after a restart I have installed the SP3 once again, it got succeeded. However when I try to use the applications, so many places I have received the error like " The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.****" . without any option, I had uninstalled the SP3 and then it started working. Any clue what could have gone wrong, as the same SP3 applied on UAT and has worked beautifully.
Sorry Vikas, no, there is no way for me to guess why your instance got locked up in that scenario.
Thanks Aaron. Any where the issue is been reported by any one? I searched a lot but could not able to get any such issue reported by some one else. Surprisingly another instance of the same environment is working as a UAT where we have initially upgraded and is working fine.