Re: Copy Database Wizard



Here is an article that list common "Copy DB Wizard" errors. I don't know
if yours is listed or not.
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues

Here are some other associated links that you may find useful:

http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's
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/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server


Personally I have never had anything but trouble with the wizard and found
that scripting the backup & restore or attach was much easier, faster and
cleaner.

--
Andrew J. Kelly SQL MVP


"Ryan" <Ryan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C1EFCDC6-B26C-4F53-B2C5-6BCC4972E4C5@xxxxxxxxxxxxxxxx
>I am in the process of consolidating 17 SQL servers into 3 (yes they
> extremely under-utilized). I am trying to use the Copy Database Wizard to
> do
> this, mostly because there are a couple hundred databases that need to be
> moved and it would be very tedious to do each one via backup and restore
> or
> detach and attach. I am having some issues with moving the logins but I
> can
> deal with that. My biggest problem is one of my target servers doesn't
> seem
> to want to accept anything from the CDW. When attempting to copy from
> Server
> A to Server B, it just locks up with no error message, no status screen,
> nothing. I can copy from A to C, or even B to C, but B just can't be the
> target for some reason. Is there a setting or configuration that I'm
> missing? Any help would be greatly appreciated. Thanks in advance.
>
> Ryan


.



Relevant Pages

  • Re: Copy database
    ... Best way is either do backup and restore or attach it. ... http://www.databasejournal.com/features/mssql/article.php/3379901 Moving ... http://www.support.microsoft.com/?id=168001 User Logon and/or Permission ... for SQL Server ...
    (microsoft.public.sqlserver.tools)
  • Re: Moving databases from SQL 7 to SQL 2000 - More Questions!
    ... want to run sp_updatestats after the restore or attach as well. ... >>There is a lot more that can go wrong with the wizard ... > SQL Server Databases ... >>Issues When a Database Is Moved Between SQL Servers ...
    (microsoft.public.sqlserver.setup)
  • Re: Migration ?
    ... During a restore, all of the metadata is upgraded. ... Moving the Master and MSDB database, what if the old server where those ... Will a restore on the SQL ... Install a SQL Server failover cluster instance ...
    (microsoft.public.sqlserver.clustering)
  • Re: deploying a database
    ... http://www.databasejournal.com/features/mssql/article.php/3379901 Moving ... Restore ... Issues When a Database Is Moved Between SQL Servers ... for SQL Server ...
    (microsoft.public.sqlserver.connect)
  • Re: Backup Users
    ... Moving DB's between ... Moving SQL Server ... > a Restore ... > "Michael Tissington" wrote in message ...
    (microsoft.public.sqlserver.programming)

Loading