Copying Database to another machine that has sql7 (HELP)

Sorry to break the threay i started earlier but once again I need this to work and I have spent al day on it with no luck.

SCOPE:
I need to copy my database from my sql server 7 platform to another office on
another server that also has sql 7. DTS will not work for me due to network traffic and so forth I would get messages saying that it failed. i tried it off/ peak time but still the same.
Now in the days of 6.5 I would be able to creat a new db device for LOAD then I would copy the dump over there and run LOAD database blab blah .. No brainer.

I have tried the following ideas some of you have mentioned such as back up the db (I would zip it copy it over there ) unzip it and tried to RESTORE it but I get the following: "The backup set holds a backup of a database other
than the existing 'mydb' database. Backup or restore operation terminiating abnormally."

I would also try restoring from FILE and I would get the similar message.
Sp_attach and detach no good either.

What am I missing. i would create a new 'mydb' then try the restore all of the above is all I get...

I am not sure why this is all day, but my books online clearly indicates the following for a restore to another server under the restore database search:
REPLACE
Specifies that SQL Server should create the specified database and its related files even if another database already exists with the same name. In such a case, the existing database is deleted. When the REPLACE option is not specified, a safety check occurs (which prevents overwriting a different database on 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
Either the database name is different from the database name recorded in the backup set,
Or

The set of files in the database is different from the set of database files contained in the backup set. Differences in file size are ignored.

When used with a file or filegroup restore operation, REPLACE allows overwriting of an existing file, which is useful only when attempting to restore a file on a disk that is replacing a failed disk.




------------
pete at 3/13/00 3:04:42 PM

Sorry to break the threay i started earlier but once again I need this to work and I have spent al day on it with no luck.

SCOPE:
I need to copy my database from my sql server 7 platform to another office on
another server that also has sql 7. DTS will not work for me due to network traffic and so forth I would get messages saying that it failed. i tried it off/ peak time but still the same.
Now in the days of 6.5 I would be able to creat a new db device for LOAD then I would copy the dump over there and run LOAD database blab blah .. No brainer.

I have tried the following ideas some of you have mentioned such as back up the db (I would zip it copy it over there ) unzip it and tried to RESTORE it but I get the following: "The backup set holds a backup of a database other
than the existing 'mydb' database. Backup or restore operation terminiating abnormally."

I would also try restoring from FILE and I would get the similar message.
Sp_attach and detach no good either.

What am I missing. i would create a new 'mydb' then try the restore all of the above is all I get...

------------
Craig at 3/13/00 3:40:50 PM

I am not sure why this is all day, but my books online clearly indicates the following for a restore to another server under the restore database search:
REPLACE
Specifies that SQL Server should create the specified database and its related files even if another database already exists with the same name. In such a case, the existing database is deleted. When the REPLACE option is not specified, a safety check occurs (which prevents overwriting a different database on 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
Either the database name is different from the database name recorded in the backup set,
Or

The set of files in the database is different from the set of database files contained in the backup set. Differences in file size are ignored.

When used with a file or filegroup restore operation, REPLACE allows overwriting of an existing file, which is useful only when attempting to restore a file on a disk that is replacing a failed disk.




------------
pete at 3/13/00 3:04:42 PM

Sorry to break the threay i started earlier but once again I need this to work and I have spent al day on it with no luck.

SCOPE:
I need to copy my database from my sql server 7 platform to another office on
another server that also has sql 7. DTS will not work for me due to network traffic and so forth I would get messages saying that it failed. i tried it off/ peak time but still the same.
Now in the days of 6.5 I would be able to creat a new db device for LOAD then I would copy the dump over there and run LOAD database blab blah .. No brainer.

I have tried the following ideas some of you have mentioned such as back up the db (I would zip it copy it over there ) unzip it and tried to RESTORE it but I get the following: "The backup set holds a backup of a database other
than the existing 'mydb' database. Backup or restore operation terminiating abnormally."

I would also try restoring from FILE and I would get the similar message.
Sp_attach and detach no good either.

What am I missing. i would create a new 'mydb' then try the restore all of the above is all I get...



Gee thanks.. But the matter of the fact is the same.. So do you have a possible resolution? Or you just want to tell me you know how to use BOL ?

Use 'restore ... with recovery'.


------------
pete at 3/13/00 3:04:42 PM

Sorry to break the threay i started earlier but once again I need this to work and I have spent al day on it with no luck.

SCOPE:
I need to copy my database from my sql server 7 platform to another office on
another server that also has sql 7. DTS will not work for me due to network traffic and so forth I would get messages saying that it failed. i tried it off/ peak time but still the same.
Now in the days of 6.5 I would be able to creat a new db device for LOAD then I would copy the dump over there and run LOAD database blab blah .. No brainer.

I have tried the following ideas some of you have mentioned such as back up the db (I would zip it copy it over there ) unzip it and tried to RESTORE it but I get the following: "The backup set holds a backup of a database other
than the existing 'mydb' database. Backup or restore operation terminiating abnormally."

I would also try restoring from FILE and I would get the similar message.
Sp_attach and detach no good either.

What am I missing. i would create a new 'mydb' then try the restore all of the above is all I get...

I have successfully transferred databases across multiple architecture using just the backup/restore process with the Enterprise Manager. The trick is, when you restore the database to the new server. You need to alter the restore as drive/path to match that of the new server. Leave the logical filename alone. This was all accomplished using the GUI.


------------
pete at 3/13/00 3:43:38 PM




------------
Craig at 3/13/00 3:40:50 PM

I am not sure why this is all day, but my books online clearly indicates the following for a restore to another server under the restore database search:
REPLACE
Specifies that SQL Server should create the specified database and its related files even if another database already exists with the same name. In such a case, the existing database is deleted. When the REPLACE option is not specified, a safety check occurs (which prevents overwriting a different database on 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
Either the database name is different from the database name recorded in the backup set,
Or

The set of files in the database is different from the set of database files contained in the backup set. Differences in file size are ignored.

When used with a file or filegroup restore operation, REPLACE allows overwriting of an existing file, which is useful only when attempting to restore a file on a disk that is replacing a failed disk.




------------
pete at 3/13/00 3:04:42 PM

Sorry to break the threay i started earlier but once again I need this to work and I have spent al day on it with no luck.

SCOPE:
I need to copy my database from my sql server 7 platform to another office on
another server that also has sql 7. DTS will not work for me due to network traffic and so forth I would get messages saying that it failed. i tried it off/ peak time but still the same.
Now in the days of 6.5 I would be able to creat a new db device for LOAD then I would copy the dump over there and run LOAD database blab blah .. No brainer.

I have tried the following ideas some of you have mentioned such as back up the db (I would zip it copy it over there ) unzip it and tried to RESTORE it but I get the following: "The backup set holds a backup of a database other
than the existing 'mydb' database. Backup or restore operation terminiating abnormally."

I would also try restoring from FILE and I would get the similar message.
Sp_attach and detach no good either.

What am I missing. i would create a new 'mydb' then try the restore all of the above is all I get...



Gee thanks.. But the matter of the fact is the same.. So do you have a possible resolution? Or you just want to tell me you know how to use BOL ?