Davide,
To restore into a database you have to make sure you are not restoring to a
physical name that already exists. When the database you are restoring into
is on the same host as the original database, the original physical name
does already exist. To get around this with TDP for SQL Version 1 you have
to create the database you are restoring into with the database's logical
names specifying different physical names. You MUST use the original
logical names.
In your case create database "restore" with logical name
"SqlPBgestitiPr_Data" specifying physical name "d:
\mssql7\data\restore_Data.MDF". You will also have to change the
transaction log location: logical name "SqlPBgestitiPr_Log" specifying
physical name "d:\mssql7\data\restore_Data.LDF", for example.
With TDP for SQL Version 2 you don't have to create the restore into
database ahead of time but you do have to specify the new physical names
for the original logical names.
Bob King [EMAIL PROTECTED]
------------------------------------
>From Davide Fanizzo:
I have to restore db in alternative DBname, so i have to use the TDPsql
command line
>From the respons of the command I understend that TDP don't take care about
/restoreinto option
03/01/2001 11:20:21,COMMAND LINE : SQLDSMC
/restorefull:SqlPBgestitiPr,02212001205512.db /recov:no
/restoreinto:restore /adsmoptf:sqldsm.opt /adsmpwd:visual
03/01/2001 11:27:19,Restored - name: SqlPBgestitiPr, type: DB, size:
1813973566, actual bytes: 0, secs: 0.00, Kb/Sec: 0.00, SQL server:
PRIVBANKSQLSERV, TSM server: sqldsm, SQL status: DB-LIB message: The file
'd:\mssql7\data\SqlPBgestitiPr_Data.MDF' cannot be used by RESTORE.
Consider using the WITH MOVE option to identify a valid location for the
file.
, TSM status: Completed
the DB "restore" exist and have the same capacity of the original
SqlPBgestitiPr
thanks for help
Davide Fanizzo
System Administrator
Banca Akros S.p.A.
tel +390243444040
cell +393488705668
