RE: Possible restore issue with 7.3.0.383 to replace database

Pete,

Here is what I did.

I created the new database under E:\applctn\ahah\devl\database with 3 files, SYS/DATA_001 and LOG_001. This is in SQL2012 running on W2K12. I had a backup taken using SQLBackup 7.1 in SQL2005 on W2K3R2 of the prod database where it resides under D:\applctn\ahah\prod\database with the same 3 files, SYS/DATA_001 and LOG_001. The backup creates two files to speed the process up.

I copied the 2 backups files to the W2K12 server. When I tried to run the script it failed because it tried to restore to D:\applctn\ahah\prod\database. Once I put the moved statements in it worked fine and replaced the original databases I had created. I had this happen to another database under the same circumstances. This made me believe that maybe the restore from script had looked at the backup files for its location information rather than the master DB locations.

We do lots of restored from production backups to at and dev servers where the file locations differ from the original ones and the script works fine. It gets its location information from the master DB rather than the backup file itself.

Can you check this out please?

Thanks

Chris