Database will not Auto-Recover

Database will not Auto-Recover

Post by Davi » Thu, 04 Oct 2001 00:45:19



Help!

    I have SQL 6.5 and every time I start it up it lists
my main production database as (recovering).  I understand
the automatic recovery process; my recovery interval is
set to 5 min.  HOWEVER, the database STAYS in this
recovering state and I cannot Back up, Restore, or Delete
the database.

    Aside from uninstalling MS SQL 6.5 and re-installing
it, what are my options to restore the production database?

Desperate Dave

 
 
 

Database will not Auto-Recover

Post by Tibor Karasz » Thu, 04 Oct 2001 01:52:32


You can get rid of the db using sp_dbremove (also, you could try DBCC DBREPAIR(..., DROPDB)).

--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sql...


Quote:> Help!

>     I have SQL 6.5 and every time I start it up it lists
> my main production database as (recovering).  I understand
> the automatic recovery process; my recovery interval is
> set to 5 min.  HOWEVER, the database STAYS in this
> recovering state and I cannot Back up, Restore, or Delete
> the database.

>     Aside from uninstalling MS SQL 6.5 and re-installing
> it, what are my options to restore the production database?

> Desperate Dave


 
 
 

Database will not Auto-Recover

Post by Keith Wo » Thu, 04 Oct 2001 03:41:12


Whoa! Before dropping any database make an NT copy/backup of the master and production db files (.DAT), including transaction logs. Will need to stop SQL Server service first. This is for precautionary
purposes.

There are a number of reasons for a long recovery. Recommend that you start with KB Article Q170115 - How to Troubleshoot Long Recovery on Databases    
to determine if recovery is still going on. If recovery appears to be hung, there could be some data integrity issues or corrupted tran log. Check SQL Errorlog for symptons.
If you don't have backups to go back to and need to salvage this database, then may want to look at Q165918 but again make copies of the master and database files first. If you have concerns about following
these steps, then I recommend that you call MS Tech Support to have a recovery specialist assist you which is well worth the effort. Recovery can be very tricky and risky.
-Keith

*****************************************************************************************
*  This posting is provided "AS IS" with no warranties, and confers no rights.                
*  You assume all risk for your use. ? 2001 Microsoft Corporation. All rights reserved
*                                                                                      
*  This is our online account name for newsgroup participation only.                    
*  Please do not send email directly to this alias.                                    
*                                                                                      
*  Helpful KB articles and whitepapers:                                                
*    Q114491 - How to Contact the Microsoft Wish Program                                
*    Q224587 - Troubleshooting Application Performance with SQL Server          
*    Q197297 - Comparison of Join Techniques                                            
*    Q258990 - Trace in SQL Server by Using Extended Stored Procedures (SQL 7.0)        
*    Q224453 - Understanding and Resolving SQL Server 7.0 Blocking Problem              
*                                                                                      
*    Coding T-SQL Like an Expert: http://msdn.microsoft.com/library/periodic/period99/sql99c4.htm                  
*                                                                                      
*    SQL Server 7.0 Query Performance Troubleshooter :  http://support.microsoft.com/support/tshoot/sql7queryperf.asp                
*                                                                                      
*  To access a KB article via Q#, type 'mskb Q#' as the URL                            
*                                                                                      
*****************************************************************************************

--------------------


|>Subject: Re: Database will not Auto-Recover
|>Date: Tue, 2 Oct 2001 18:52:32 +0200

|>
|>You can get rid of the db using sp_dbremove (also, you could try DBCC DBREPAIR(..., DROPDB)).
|>
|>--
|>Tibor Karaszi, SQL Server MVP
|>Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sql...
|>
|>
|>

|>> Help!
|>>
|>>     I have SQL 6.5 and every time I start it up it lists
|>> my main production database as (recovering).  I understand
|>> the automatic recovery process; my recovery interval is
|>> set to 5 min.  HOWEVER, the database STAYS in this
|>> recovering state and I cannot Back up, Restore, or Delete
|>> the database.
|>>
|>>     Aside from uninstalling MS SQL 6.5 and re-installing
|>> it, what are my options to restore the production database?
|>>
|>> Desperate Dave
|>
|>
|>

 
 
 

Database will not Auto-Recover

Post by oj » Thu, 04 Oct 2001 03:54:18


keith,

you're pretty *active* in this ng! way go.

-oj


Quote:> Whoa! Before dropping any database make an NT copy/backup of the master

and production db files (.DAT), including transaction logs. Will need to
stop SQL Server service first. This is for precautionary
Quote:> purposes.

> There are a number of reasons for a long recovery. Recommend that you

start with KB Article Q170115 - How to Troubleshoot Long Recovery on
Databases
Quote:> to determine if recovery is still going on. If recovery appears to be

hung, there could be some data integrity issues or corrupted tran log. Check
SQL Errorlog for symptons.
Quote:> If you don't have backups to go back to and need to salvage this database,

then may want to look at Q165918 but again make copies of the master and
database files first. If you have concerns about following
Quote:> these steps, then I recommend that you call MS Tech Support to have a

recovery specialist assist you which is well worth the effort. Recovery can
be very tricky and risky.
Quote:> -Keith

****************************************************************************
*************
Quote:> *  This posting is provided "AS IS" with no warranties, and confers no
rights.
> *  You assume all risk for your use. ? 2001 Microsoft Corporation. All
rights reserved
> *
> *  This is our online account name for newsgroup participation only.
> *  Please do not send email directly to this alias.
> *
> *  Helpful KB articles and whitepapers:
> *    Q114491 - How to Contact the Microsoft Wish Program
> *    Q224587 - Troubleshooting Application Performance with SQL Server
> *    Q197297 - Comparison of Join Techniques
> *    Q258990 - Trace in SQL Server by Using Extended Stored Procedures
(SQL 7.0)
> *    Q224453 - Understanding and Resolving SQL Server 7.0 Blocking Problem
> *
> *    Coding T-SQL Like an Expert:

http://msdn.microsoft.com/library/periodic/period99/sql99c4.htm
Quote:> *
> *    SQL Server 7.0 Query Performance Troubleshooter :

http://support.microsoft.com/support/tshoot/sql7queryperf.asp
Quote:> *
> *  To access a KB article via Q#, type 'mskb Q#' as the URL
> *

****************************************************************************
*************
Quote:

> --------------------
> |>From: "Tibor Karaszi"



> |>Subject: Re: Database will not Auto-Recover
> |>Date: Tue, 2 Oct 2001 18:52:32 +0200

> |>
> |>You can get rid of the db using sp_dbremove (also, you could try DBCC

DBREPAIR(..., DROPDB)).
Quote:> |>
> |>--
> |>Tibor Karaszi, SQL Server MVP
> |>Archive at:

http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sql...

- Show quoted text -

> |>
> |>
> |>


> |>> Help!
> |>>
> |>>     I have SQL 6.5 and every time I start it up it lists
> |>> my main production database as (recovering).  I understand
> |>> the automatic recovery process; my recovery interval is
> |>> set to 5 min.  HOWEVER, the database STAYS in this
> |>> recovering state and I cannot Back up, Restore, or Delete
> |>> the database.
> |>>
> |>>     Aside from uninstalling MS SQL 6.5 and re-installing
> |>> it, what are my options to restore the production database?
> |>>
> |>> Desperate Dave
> |>
> |>
> |>