Copying Databases From Server to Another

What is the best and safest way to copy about 55 Databases from a server
running win2k to a new server running Win Server 2003 Ent. Ed. What are
the different options do i have? Can I copy all the current Db plans, jobs,
and Logins? What is a good practice for doing this? The win2k server is in
production right now. Do i have to shut it down?
Please Help. Thanks
hi,
"Shash Goyal" <Shash703@.gmail.com> ha scritto nel messaggio
news:uEjQ2LwtEHA.2808@.TK2MSFTNGP14.phx.gbl
> What is the best and safest way to copy about 55 Databases from a
> server running win2k to a new server running Win Server 2003 Ent. Ed.
> What are the different options do i have? Can I copy all the current
> Db plans, jobs, and Logins? What is a good practice for doing this?
> The win2k server is in production right now. Do i have to shut it
> down?
> Please Help. Thanks
wow... a massive task, isn't it? =;-D
I'd suggest, if available, the Copy database wizard, available in Enterprise
Manager, for SQL Server instances, which takes care to move logins and msdb
objects too...
but... if you are on MSDE, you do not have access to it... an all becomes
trickier...
you can perhaps full backup and restore on the new server users databases...
this will not move the logins...
you could then script the logins out and recreate them on the destination
server... keep in mind you will require some login/user sync, as better
explained in
http://www.sqlservercentral.com/colu...okenlogins.asp
as regard msdb objects... script them out too, and recreate tem form their
DDL sql scripts in the destination server...
you are not required to shut down the original server, this way... nor if
you can use Copy database EM wizard... you are required to temporary have
you server down, in someway, if you detach/reattach your user databases...
but I'd prefer the full backup/restore method in this particular scenario..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you Andrea!!!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2tpjc9F2386efU1@.uni-berlin.de...
> hi,
> "Shash Goyal" <Shash703@.gmail.com> ha scritto nel messaggio
> news:uEjQ2LwtEHA.2808@.TK2MSFTNGP14.phx.gbl
> wow... a massive task, isn't it? =;-D
> I'd suggest, if available, the Copy database wizard, available in
Enterprise
> Manager, for SQL Server instances, which takes care to move logins and
msdb
> objects too...
> but... if you are on MSDE, you do not have access to it... an all becomes
> trickier...
> you can perhaps full backup and restore on the new server users
databases...
> this will not move the logins...
> you could then script the logins out and recreate them on the destination
> server... keep in mind you will require some login/user sync, as better
> explained in
> http://www.sqlservercentral.com/colu...okenlogins.asp
> as regard msdb objects... script them out too, and recreate tem form their
> DDL sql scripts in the destination server...
> you are not required to shut down the original server, this way... nor if
> you can use Copy database EM wizard... you are required to temporary have
> you server down, in someway, if you detach/reattach your user databases...
> but I'd prefer the full backup/restore method in this particular
scenario..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>