I ran this script to backup to restore a backup onto a database with a new
name - on the same server.
USE master
> RESTORE DATABASE DBnew
> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
> with RECOVERY,
> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
> REPLACE
When I look at the properties for the database under em, I see that both the
original database and the copy-of-it-with-a-new-name have the same "File
Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
"Transaction Files" tabs. The "Location", which points to the actual
physical file, is correctly and uniquely named.
Is the fact that these have the same File Name going to confuse SQL Server
when it goes to update a database?You should be fine.
"MarkAurit" <MarkAurit@.discussions.microsoft.com> wrote in message
news:59CC2C26-13F8-4664-99F1-CC550827A9D4@.microsoft.com...
>I ran this script to backup to restore a backup onto a database with a new
> name - on the same server.
> USE master
>> RESTORE DATABASE DBnew
>> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
>> with RECOVERY,
>> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
>> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
>> REPLACE
> When I look at the properties for the database under em, I see that both
> the
> original database and the copy-of-it-with-a-new-name have the same "File
> Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
> "Transaction Files" tabs. The "Location", which points to the actual
> physical file, is correctly and uniquely named.
> Is the fact that these have the same File Name going to confuse SQL Server
> when it goes to update a database?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment