Post reply

Recovering Suspected database

  • December 15, 2003 at 12:29 am

    #65764

    I have a situation where in a production database has been marked suspected by the SQL server. I have tried recovering the database through some methods posted in some other site but of no use. The procedures tend to work when you only have a primary log file but in my case I have a secondary log file also. If somebody has tried recovering a suspected database do revert back.

  • December 15, 2003 at 3:07 am

    #486120

    I assume you are referring to the standard suggestion of detaching a database and then re-attaching it without the logfile(s), which will create a new clean log file and if you're lucky you'll end up with a working, non-suspect database. I had the same issue some weeks ago, a database marked as suspect that wasn't possible to fix using any technique I know of. So I thought that I'd as a last resort detach it and use the above technique, but alas, you cannot attach a database without it's logfiles if it has more than one log file. I ended up using a backup.

    I guess you have tried the standard techniques for removing the suspect status? Remove flag, create extra file and then try recovery.

    --

    Chris Hedgate @ Extralives (http://www.extralives.com/)

    Co-author of Best of SQL Server Central 2002 (http://www.sqlservercentral.com/bestof/)

    Articles: http://www.sqlservercentral.com/columnists/chedgate/

    --
    Chris Hedgate http://www.hedgate.net/
    Contributor to the Best of SQL Server Central volumes
    Articles: http://www.sqlservercentral.com/columnists/chedgate/

  • December 16, 2003 at 8:19 am

    #486412

    Could you please post the steps you took

    Mike

  • December 16, 2003 at 8:20 am

    #486413

    I have come across this issue several times. When ALL else fails, you can always put the database in emergency mode, recreate all the tables in a new database, copy all the data to the new database, drop the suspect database. The last step is optional which is to rename the database and its log files to the original name of the suspect database.

    As I said before, this is a last result type of solution. There is a reason that the mode is called emergency.

    I have had to do this enough times that I finally created a series of scripts that get me through the process.

    Steve

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply