Post reply

Restore Database Fails

  • October 28, 2005 at 8:10 am

    #110678

    Using SQL Server 2000 on a Windows Server 2003 box.  We have multiple db's on this box, but one specific db; when we try to use the Restore Database command, enterprise manager just stops responding.  We have a database maintenance plan that backs up the db every 8 hours and backs up the log evey 10 minutes.  I checked the properties/options of this db compared to others and it is setup the same.

    Thanks in advance for your help.

    Hospo

  • October 28, 2005 at 10:17 am

    #600984

    any size differences between the specific database and the others?

  • October 28, 2005 at 10:23 am

    #600988

    'enterprise manager just stops responding'

     

    What do you mean by stops responding??  Many times EM appears to be hung whild performing restores due to the backup file / DB size as it has to read from the backup file and do some pre-restore operations.  EM may even appear as 'not responding' in Windows Task Manager, but this does not mean that EM is truely hung.  How long do you leave it before you decide it is not responding?

    John Rowan

    ======================================================
    ======================================================
    Forum Etiquette: How to post data/code on a forum to get the best help[/url] - by Jeff Moden

  • October 28, 2005 at 10:24 am

    #600991

    Dont forget you can restore from the QA using something like:

    restore database JUNKNAME from disk="c:\righthere\junk.bak'

    See BOL for more on Restore.

    It is worth a shot to see if it bombs out too.

  • October 28, 2005 at 11:25 am

    #601016

    I left Enterprise manager run over 5 minutes and the wizard never even came up to begin the restore process.  On other db's the wizard opens to begin the restore process within about 15 seconds.  The backup file size is only about 26 Mb.

  • October 28, 2005 at 11:37 am

    #601022

    So this is before you even get to select the restore options?? Ouch....Is this a production DB?  Even so, if you must do a restore, you may have to detach the DB, create a new DB (rename the original DB and log files if needed) and restore the backup to the new DB. 

    John Rowan

    ======================================================
    ======================================================
    Forum Etiquette: How to post data/code on a forum to get the best help[/url] - by Jeff Moden

  • October 28, 2005 at 11:39 am

    #601023

    Yes, this is a production db.

  • October 28, 2005 at 11:45 am

    #601026

    Judging from the size of the backup file, 26MB, this is a relatively small DB.  Knowing that you must restore the DB, it is obvious that you are aware that a production outage must occur (unless you are planning on doing this during a maintenance window).  You may want to detach/recreate your DB as I suggested in the previous posting.  Has the backup been verified  (by a full restore and not the 'verify backup' option)?  If your backup file is good, this may be your only option.  Some of the more seasoned forum members may have more insight into this one, but my solution will work in getting your DB restored.

    John Rowan

    ======================================================
    ======================================================
    Forum Etiquette: How to post data/code on a forum to get the best help[/url] - by Jeff Moden

  • October 28, 2005 at 12:09 pm

    #601044

    Thanks a bunch!  We will plan a maintenance schedule and follow your suggestion.

Viewing 9 posts - 1 through 8 (of 8 total)

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