InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 23:31:03 GMT20http://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxPlease post your question in a new thread and include as much detail as possible about what events preceded the problem and what errors are in the error log.Thu, 11 Apr 2013 05:15:16 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxHi all,My database is showing as RECOVERY_PENDING any one can help me ?Thu, 11 Apr 2013 05:07:58 GMTsoorajsahadevhttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspx[quote][b]ericjorg (4/9/2013)[/b][hr][quote][b]GilaMonster (4/9/2013)[/b][hr]Good way to destroy a database...[url]http://sqlinthewild.co.za/index.php/2009/06/09/deleting-the-transaction-log/[/url][/quote]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.[/quote]Very exceptional situation then. Normally deleting the log of a database that's in recovery will make the database recovery_pending, deleting the log of a database that's recovery pending will result in it still being in the recovery pending state.Tue, 09 Apr 2013 13:08:53 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspx[quote][b]GilaMonster (4/9/2013)[/b][hr]Good way to destroy a database...[url]http://sqlinthewild.co.za/index.php/2009/06/09/deleting-the-transaction-log/[/url][/quote]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.Tue, 09 Apr 2013 13:02:45 GMTericjorghttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspx[quote][b]ericjorg (4/9/2013)[/b][hr]I had this issue on Sql 2012 and fixed it this way:1) Stop SQL2) Delete the recovering database's log file3) Start SQL[/quote]Good way to destroy a database...[url]http://sqlinthewild.co.za/index.php/2009/06/09/deleting-the-transaction-log/[/url]Tue, 09 Apr 2013 12:49:56 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxI had this issue on Sql 2012 and fixed it this way:1) Stop SQL2) Delete the recovering database's log file3) Start SQLTue, 09 Apr 2013 12:39:14 GMTericjorghttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxThanks 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)".CheersDavid.Mon, 25 Mar 2013 20:50:47 GMTdwe71http://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxCheck this,This might helphttp://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/835dee9b-0993-433f-baf7-a646dfa7f8f7Tue, 12 Feb 2013 02:52:39 GMTshankar.guravhttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxThanks Its working For meFri, 31 Aug 2012 01:03:49 GMTjayantjhttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxI had tried but it showing in restoring state...Wed, 08 Aug 2012 00:19:54 GMTdineshvishehttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxGoodmorning,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.RegardsSrikanth Reddy KundurFri, 22 Jun 2012 10:57:02 GMTksrikanth77http://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxI 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.Thu, 21 Jun 2012 11:05:57 GMTjswong05http://www.sqlservercentral.com/Forums/Topic730583-146-1.aspx[quote][b]iqbal1258 (10/19/2011)[/b][hr]Hey Guys Nothin to do....Chek firs mdf and ldf is exist or not..if exist run below coommand on master DBALTER DATABASE 'DATBASE NAME' SET OFFLINE WITH ROLLBACK IMMEDIATEALTER DATABASE 'DATBASE NAME' SET ONLINE WITH ROLLBACK IMMEDIATE[/quote]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.Tue, 17 Apr 2012 12:44:35 GMTjohn.danleyhttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspx[quote][b]iqbal1258 (10/19/2011)[/b][hr]Hey Guys Nothin to do....Chek firs mdf and ldf is exist or not..if exist run below coommand on master DBALTER DATABASE 'DATBASE NAME' SET OFFLINE WITH ROLLBACK IMMEDIATEALTER DATABASE 'DATBASE NAME' SET ONLINE WITH ROLLBACK IMMEDIATE[/quote]Why you want to do this?Thu, 20 Oct 2011 02:35:04 GMTmuthukkumaran Kaliyamoorthyhttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxHey Guys Nothin to do....Chek firs mdf and ldf is exist or not..if exist run below coommand on master DBALTER DATABASE 'DATBASE NAME' SET OFFLINE WITH ROLLBACK IMMEDIATEALTER DATABASE 'DATBASE NAME' SET ONLINE WITH ROLLBACK IMMEDIATEWed, 19 Oct 2011 18:32:10 GMTiqbal1258http://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxJust as an FYI, in case it helps anyone...We recently had this same problem. One of our DBs was stuck in a "Recovery Pending" state following a sudden (and unusual) loss of power. (An onsite electrician was to blame.)Anyhow, it turns out that when the server booted back up, the various drives were a little slower to come online. As a result, when SQL Server went to restore the DB, the drives on which the needed data is stored weren't yet available. (The error logs pointed to which drives were needed).Once the drives were available, a manual restart of SQL Server fixed the problem and the DB was automatically recovered.CheersMon, 01 Nov 2010 16:23:04 GMTsickpuphttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxPlease post new questions in a new thread.ThanksTue, 07 Sep 2010 13:08:20 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxHelloUnfortunatelly I am having a simillar issue and waiting for the database to recover seems not to work for me. The database seems to be stuck in RECOVERING state.Moreover, if I restart SQL Server, other databases start to have the same issue, meaning they become stuck in RECOVERING mode too, while other database seem to have been recovered.Now, even msdb is in RECOVERING state.Any help on this would be greatly appreciated.Thanks,IoanaTue, 07 Sep 2010 12:19:10 GMTioana-477197http://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxThanks, this worked for me!Cheers,Jeremy.Wed, 13 Jan 2010 17:17:50 GMTjnieuwoudthttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspx[quote][b]Krishna Potlakayala (6/8/2009)[/b][hr]Yes, the server is recovering the database. Was there any sudden shut down of the SQL Server? Just wait till it comes back online again. [/quote]That's true of the state RECOVERING. Recovery Pending means that recovery cannot be started. Until the cause is fixed, recovery cannot run and the DB cannot come online.Mon, 08 Jun 2009 05:45:52 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxRecovery pending means that for some reason SQL cannot run restart recovery on the database. Usually this is because the log is missing or corrupt.[quote]"G:\Data\MSSQL\Database.mdf"."G:\Data\MSSQL\Data\Database_log.ldf"[/quote]Do these files exist? Is the drive online and available? If so, try stopping and restarting the SQL service as it may be that SQL came up before the drive was available. That would have caused this error.Mon, 08 Jun 2009 05:43:13 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic730583-146-1.aspx[quote][b]santhosh (6/8/2009)[/b][hr]One of my databases is in [b]Recovery pending[/b] state. I tried to run an Alter command on the database to set it in Online state but it throws the following error.Msg 5120, Level 16, State 101, Line 1Unable to open the physical file "G:\Data\MSSQL\Database.mdf". Operating system error 3: "3(The system cannot find the path specified.)".File activation failure. The physical file name "G:\Data\MSSQL\Data\Database_log.ldf" may be incorrect.Msg 945, Level 14, State 2, Line 1Database 'Database' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.Msg 5069, Level 16, State 1, Line 1Thanx in advance for any help ![/quote]Yes, the server is recovering the database. Was there any sudden shut down of the SQL Server? Just wait till it comes back online again. What does your error logs say?Mon, 08 Jun 2009 05:22:36 GMTmaechismo_8514http://www.sqlservercentral.com/Forums/Topic730583-146-1.aspxOne of my databases is in [b]Recovery pending[/b] state. I tried to run an Alter command on the database to set it in Online state but it throws the following error.Msg 5120, Level 16, State 101, Line 1Unable to open the physical file "G:\Data\MSSQL\Database.mdf". Operating system error 3: "3(The system cannot find the path specified.)".File activation failure. The physical file name "G:\Data\MSSQL\Data\Database_log.ldf" may be incorrect.Msg 945, Level 14, State 2, Line 1Database 'Database' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.Msg 5069, Level 16, State 1, Line 1Thanx in advance for any help !Mon, 08 Jun 2009 04:52:51 GMTSanz