without any option, I had uninstalled the SP3 and then it started working.

Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.****'. Rerun your statement when there are fewer active users. 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. Then after a restart I have installed the SP3 once again, it got succeeded. But when I tried to login, I got message like 'DB is in script upgrade mode, Only administrator can login'. Then I tried copying that file from UAT env and could able to start the SQL. When I tried to start the SQL it did not and was asking for some resourcefile not available.

Not sure the reason but the NW team was working some port changes. I have installed the SP3, however in between I have received one issue as NTservice could not start. 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. 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). Better yet, if you're on 2008 R2, please see my post where I announce new CUs for the 2008 R2 branches: Branch Please check If it reports, or, please go re-download and re-apply the relevant cumulative update for your branch. So if you download today, you'll actually get: Branch On June 13th, both articles were updated with new versions of the cumulative updates that no longer exhibit this symptom ( sound familiar?). 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. 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).

In April and May, Microsoft released cumulative updates for SQL Server 20 R2 (I blogged about them here and here). They are: Branch

Download sql server 2008 r2 sp3