Maria,
Please obtain the latest version of TDP for Microsoft SQL.
You should have version 1.1.2.
The new version of the User's Guide discusses this issue
under the "/RESTOREINTO" option of the "/RESTOREFULL command".
An exerpt:
=====================================================================
/RESTOREINTO:dbname
This parameter specifies the name of a database to restore into.
This allows you to restore one database into another database.
Note: In SQL Server 7.0, databases are defined with logical
files that are mapped to physical files. The database
name identified within the /restoreinto parameter must
be pre-defined with the exact same logical name that
existed in the original database being restored but
with different a physical file name. For example,
if the original database being restored (OldDb) consists of:
Logical File Name Physical File Name
OldDb_Data c:\NewDb_Data.MDF
OldDb2_Data c:\NewDb2_Data.NDF
OldDb_Log e:\NewDb_Log.LDF
Then in order to perform /restoreinto:NewDb while the
original database still exists, the new database must
be predefined as:
Logical File Name Physical File Name
OldDb_Data d:\NewDb_Data.MDF
OldDb2_Data d:\NewDb2_Data.NDF
OldDb_Log d:\NewDb_Log.LDF
=====================================================================
Thanks,
Del
----------------------------------------------------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
Maria Ragan <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 09/27/2000 04:37:11 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Connect Agemt Error
SQL 7/NT4/ADSM Connect Agent 1.1.1A
Trying to restore a production database into a new database created for the
recovery. Getting the following error:
Error: SQL server errors encountered. DB_LIB message: The file
e:\mssql7\data\dbname.mdf
cannot be used by Restore. Consider using the WITH MOVE option to
identify a valid location for this file.
Read on this site that for SQL 7.0 they require the original database file
(.mdf file) to NOT exist before doing a "restore into". The suggestion was
to rename the database .mdf file to something else or restore to a
different
SQL server.
However, DBA has told me that the database is empty. It was created just
to
house this load from production. What are we missing?
Thanks,
Maria
Maria Ragan
Mid Range Systems
Bear Creek Corporation
