Is this a one shot deal or will this be part of a production script? I
would go with either a detach and attach or a backup and restore over the
copy db task myself. Here are some links that may help:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=274463 Copy DB
Wizard issues
--
Andrew J. Kelly
SQL Server MVP
"Stressed" <k@c.co.uk> wrote
Quote:
SQL 2000.
Hopefully I've the right newsgroup for this one.
I'm attempting to write a script, to enable me to move databases across
servers.
The problem I'm hitting, is how to specify that the data file locations on
the target
server are different from those on the source server. The transfer object
doesn't
seem to allow this or I can't find where it does.
If anybody can help me with this, or simply advise whether a brute force
attach/copy/reattach
approach would be best I would be most grateful.
TIA. |