Migrate SQL Server 2000

Hello. We have a new database server machine that will replace our old
database server machine running SQL 2000 (will take on the same name and ip
address). I was wondering if anyone could recommend or point me to some
info on what is the best method in getting the data from our old soon to be
retired machine to our new machine? Perhaps setting up an empty SQL 2000 on
the new machine and then taking the backup files from the old machine and
doing a restore on each database starting with the master db?...just
wondering if this will affect any of the system databases (master, temp,
msdb, model) like the sql/window logins/passwords and/or other backend
things that should or would need to remain in tact?
Thanks in advance.
Jhttp://www.microsoft.com/downloads/...&DisplayLang=en
This is What you can Read or goto
http://www.microsoft.com/downloads/...&displaylang=en
This is Helpful.
Rest in Short: Just Detach and attach the Databases to the new SQL2K5
Server and change the Compatability Level to 90
As for the DTS PAckages you might have on SQL2000, Well its a whole new
Story. DTS Packages without several connections are easy to migrate,
but Some require to be recreated from Scratch, if you have on of those
smart Developers with you, He will figure out a process in time.
Maninder
MCDBA
On Jan 22, 1:54 pm, "J" <IDontLikeS...@.Nowhere.com> wrote:
> Hello. We have a new database server machine that will replace our old
> database server machine running SQL 2000 (will take on the same name and i
p
> address). I was wondering if anyone could recommend or point me to some
> info on what is the best method in getting the data from our old soon to b
e
> retired machine to our new machine? Perhaps setting up an empty SQL 2000
on
> the new machine and then taking the backup files from the old machine and
> doing a restore on each database starting with the master db?...just
> wondering if this will affect any of the system databases (master, temp,
> msdb, model) like the sql/window logins/passwords and/or other backend
> things that should or would need to remain in tact?
> Thanks in advance.
> J|||Actually both old and new server will be SQL 2000. So I guess I can look at
my first task as a full restore based on all of the backups?
I think we will eventually upgrade to SQL 2005 so I'll definitely keep your
helpful info in mind. Thanks for the info Maninder. I totally appreciate
it.
J
"Maninder" <msdhanjal@.gmail.com> wrote in message
news:1169493039.530765.30020@.s34g2000cwa.googlegroups.com...
> http://www.microsoft.com/downloads/...&DisplayLang=en
> This is What you can Read or goto
> http://www.microsoft.com/downloads/...&displaylang=en
> This is Helpful.
> Rest in Short: Just Detach and attach the Databases to the new SQL2K5
> Server and change the Compatability Level to 90
> As for the DTS PAckages you might have on SQL2000, Well its a whole new
> Story. DTS Packages without several connections are easy to migrate,
> but Some require to be recreated from Scratch, if you have on of those
> smart Developers with you, He will figure out a process in time.
> Maninder
> MCDBA
>
> On Jan 22, 1:54 pm, "J" <IDontLikeS...@.Nowhere.com> wrote:
>|||You could either:
-. Do a back up the database on your old database and restore of your
database on your new server.
-. Do an dettach and attach of your database data and log file.
Personally, I usually choose the backup and restore approach, just as you
said. Also you might need to restore the system databases: master, and msdb
(at the very least), if you want to bring over the login information, and
also the job information. If you want you can also backup and restore the
model database.
http://msdn2.microsoft.com/en-us/library/ms190190.aspx
Lucas
For info on backup and restore system database:
"J" wrote:

> Actually both old and new server will be SQL 2000. So I guess I can look
at
> my first task as a full restore based on all of the backups?
> I think we will eventually upgrade to SQL 2005 so I'll definitely keep you
r
> helpful info in mind. Thanks for the info Maninder. I totally appreciate
> it.
> J
> "Maninder" <msdhanjal@.gmail.com> wrote in message
> news:1169493039.530765.30020@.s34g2000cwa.googlegroups.com...
>
>|||Thanks for the insightful info Lucas. Mucha appreciated.
Take care,
J
"Lucas Kartawidjaja" <LucasKartawidjaja@.discussions.microsoft.com> wrote in
message news:A92C9C5E-10EE-4182-8ED3-2B44450BC793@.microsoft.com...[vbcol=seagreen]
> You could either:
> -. Do a back up the database on your old database and restore of your
> database on your new server.
> -. Do an dettach and attach of your database data and log file.
> Personally, I usually choose the backup and restore approach, just as you
> said. Also you might need to restore the system databases: master, and
> msdb
> (at the very least), if you want to bring over the login information, and
> also the job information. If you want you can also backup and restore the
> model database.
> http://msdn2.microsoft.com/en-us/library/ms190190.aspx
> Lucas
> For info on backup and restore system database:
>
> "J" wrote:
>