What are the challenges you face when working across database platforms? Take the survey

Restore problem

rbvdbergrbvdberg Posts: 14
edited May 27, 2007 11:42PM in SQL Backup Previous Versions

Yesterday I tried to restore a large database (8 files of 8 GB). The backup took 1,5 hours, but the restore wasn't finished after 20 hours, so I stopped the restore.
When I try to do a restore headeronly, that doesn't restore any information. Does that mean my backup is corrupt?


  • Options
    peteypetey Posts: 2,358 New member
    When you run RESTORE HEADERONLY via SQL Backup, it will also need to read the entire file. You will encounter the same issue as the full restore.

    When you run the restore, run the sqbstatus extended stored procedure from another connection. Is there any progress reported? Note that if you are restoring a new database, SQL Server will first need to create the database files. During this process, sqbstatus will not report any progress. Only after the files have been created will the restore process actually start.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.