Database in Recovery Pending State

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » Database in Recovery Pending State

23 posts, Page 2 of 3

««1 2 3 »»

Database in Recovery Pending State

Rate Topic

Display Mode

Topic Options

Author

Message

john.danley

Posted Tuesday, April 17, 2012 12:44 PM

Valued Member

Group: General Forum Members
Last Login: 2 days ago @ 3:34 PM
Points: 54, Visits: 298

iqbal1258 (10/19/2011)

Hey Guys Nothin to do....

Chek firs mdf and ldf is exist or not..
if exist run below coommand on master DB

ALTER DATABASE 'DATBASE NAME' SET OFFLINE WITH ROLLBACK IMMEDIATE
ALTER DATABASE 'DATBASE NAME' SET ONLINE WITH ROLLBACK IMMEDIATE

Funny you should post this today. I was asked to help with a similar issue this morning. DB would not come online posting error - insufficient disk space or memory. There was plenty of disc space, but memory was a bit over-taxed. One thing I did note was the ldf was 2+ times larger than the mdf at around 58GB which raises other flags. I ended up doing just this, setting the db offline then online. It took over an hour to come up, but did succeed and we were back in business after doing a little clean-up on the DB.

Post #1285191

jswong05

Posted Thursday, June 21, 2012 11:05 AM

SSC Rookie

Group: General Forum Members
Last Login: Monday, March 18, 2013 7:54 AM
Points: 27, Visits: 421

I had all databases in "recovery pending" not because of disks nor memory. It was from SQL Server upgrade running into an error. The error was caused by 3rd party software had customized SSRS config (non-microsoft tags in rsreportserver.config). I removed the cause, upgraded the database instance, remove the databases (make sure you don't damage all the data and log files), re-attach them back. Violla, they are working again like brand new.

Jason
http://dbace.us
Tongue

Post #1319478

ksrikanth77

Posted Friday, June 22, 2012 10:57 AM

Valued Member

Group: General Forum Members
Last Login: Friday, May 10, 2013 5:51 PM
Points: 54, Visits: 121

Goodmorning,

We had a same issue when one of our VM had a problem with the drives and had some maintnenace, but it was resolved after a restart. However there is also a workaround which worked for me through GUI jus change the Recovery model to simple from or vice versa, this will resolve the issue.

Regards
Srikanth Reddy Kundur

Post #1320115

dineshvishe

Posted Wednesday, August 08, 2012 12:19 AM

Grasshopper

Group: General Forum Members
Last Login: Yesterday @ 9:54 PM
Points: 16, Visits: 173

I had tried but it showing in restoring state...

Post #1341693

jayantj

Posted Friday, August 31, 2012 1:03 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, November 28, 2012 6:16 AM
Points: 1, Visits: 5

Thanks Its working For me

Post #1352618

shankar.gurav

Posted Tuesday, February 12, 2013 2:52 AM

Forum Newbie

Group: General Forum Members
Last Login: Tuesday, February 12, 2013 2:52 AM
Points: 1, Visits: 9

Check this,

This might help
http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/835dee9b-0993-433f-baf7-a646dfa7f8f7

Post #1418819

dwe71

Posted Monday, March 25, 2013 8:50 PM

Forum Newbie

Group: General Forum Members
Last Login: Saturday, May 04, 2013 11:06 AM
Points: 5, Visits: 34

Thanks a lot - restarting the service worked for me. Still no idea why this happened, unless maybe I forgot to detach the database last time I opened SQL Server Management Studio, and/or used it in database view in Visual Studio in the meantime.
The service name for me was "MSSQL$SQLEXPRESS", with a display name "SQL Server (SQLEXPRESS)".
Cheers
David.

Post #1435238

ericjorg

Posted Tuesday, April 09, 2013 12:39 PM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, May 09, 2013 11:57 AM
Points: 2, Visits: 3

I had this issue on Sql 2012 and fixed it this way:

1) Stop SQL
2) Delete the recovering database's log file
3) Start SQL

Post #1440502

GilaMonster

Posted Tuesday, April 09, 2013 12:49 PM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 12:59 PM
Points: 37,640, Visits: 29,895

ericjorg (4/9/2013)

I had this issue on Sql 2012 and fixed it this way:

1) Stop SQL
2) Delete the recovering database's log file
3) Start SQL

Good way to destroy a database...
http://sqlinthewild.co.za/index.php/2009/06/09/deleting-the-transaction-log/

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1440506

ericjorg

Posted Tuesday, April 09, 2013 1:02 PM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, May 09, 2013 11:57 AM
Points: 2, Visits: 3

GilaMonster (4/9/2013)

Good way to destroy a database...
http://sqlinthewild.co.za/index.php/2009/06/09/deleting-the-transaction-log/

Yes, that is exactly right. In my case, this was a test database and the logfile was created in a different version of SQL server, so it was safe to wipe it out.

Post #1440511

« Prev Topic | Next Topic »

23 posts, Page 2 of 3

««1 2 3 »»

Permissions