Comments on: Restore an MSSQL backup to a different database name http://blog.7deeds.com/2008/12/24/restore-an-mssql-backup-to-a-different-database-name/ Petros Amiridis - A humble programmer's seven noteworthy actions for the community Mon, 06 Sep 2010 08:52:59 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Petros http://blog.7deeds.com/2008/12/24/restore-an-mssql-backup-to-a-different-database-name/comment-page-1/#comment-1941 Petros Fri, 25 Sep 2009 19:13:09 +0000 http://blog.7deeds.com/?p=78#comment-1941 <a href="#comment-1940" rel="nofollow">@Derek </a> Thanks for commenting. I don't know why it didn't work for you without the REPLACE, but I have found the following excerpt: -----%<------------------ When the REPLACE option is not specified, a safety check occurs (which prevents overwriting a different database by accident). The safety check ensures that the RESTORE DATABASE statement will not restore the database to the current server if: The database named in the RESTORE statement already exists on the current server, and The database name is different from the database name recorded in the backup set. REPLACE also allows RESTORE to overwrite an existing file which cannot be verified as belonging to the database being restored. Normally, RESTORE will refuse to overwrite pre-existing files. -----%<------------------ Maybe something mentioned above was your case. @Derek

Thanks for commenting. I don’t know why it didn’t work for you without the REPLACE, but I have found the following excerpt:

—–%<——————
When the REPLACE option is not specified, a safety check occurs (which
prevents overwriting a different database by accident). The safety check
ensures that the RESTORE DATABASE statement will not restore the database to
the current server if:

The database named in the RESTORE statement already exists on the current
server, and

The database name is different from the database name recorded in the backup
set.

REPLACE also allows RESTORE to overwrite an existing file which cannot be
verified as belonging to the database being restored. Normally, RESTORE will
refuse to overwrite pre-existing files.
—–%<——————

Maybe something mentioned above was your case.

]]> By: Derek http://blog.7deeds.com/2008/12/24/restore-an-mssql-backup-to-a-different-database-name/comment-page-1/#comment-1940 Derek Fri, 25 Sep 2009 17:05:08 +0000 http://blog.7deeds.com/?p=78#comment-1940 Why is the replace required here? What is replace doing? I've been having issues getting a particular DB to restore as a different name, and with a test db I was able to do something like... restore database testdb from disk = C:\test.bak with recovery, move 'test' to 'C:\newlo\test.mdf', move 'test_Log' to 'c:\newlo\test.ldf' and that worked, but then on this production DB, when I tried the same I kept getting failures until I used replace/go as you did above. Why is the replace required here? What is replace doing? I’ve been having issues getting a particular DB to restore as a different name, and with a test db I was able to do something like…

restore database testdb from disk = C:\test.bak with recovery,
move ‘test’ to ‘C:\newlo\test.mdf’,
move ‘test_Log’ to ‘c:\newlo\test.ldf’
and that worked, but then on this production DB, when I tried the same I kept getting failures until I used replace/go as you did above.

]]>