Move DBs to new server?

Hi,
I have 12 databases running on SQL Server 2000 on Windows 2000, and would
like to move them all to new hardware comprising Windows Server 2003 running
SQL Server 2000. I already have SQL Server installed on the new box. In
theory it's simple, but I have some questions:
1. Database security, logins, ownership etc; I hope to give the new server
the same name as the old server but it will have a different SID and I don't
know if there are any issues with that?
2. Merely restoring "user" databases to the new server means I will lose all
kinds of useful configuration data such as my record of backups? Do I also
have to restore Master, Model, MSDB, tempDB?
3. Is it best to detach/attach, or use backup/restore? If I use
backup/restore I'm confused about the tLog restore. I used to think if you
made a "full" backup you didn't need a tLog, but now I'm not sure, and the
SQL Server Books on-line example of using tLog backup and restore seems far
from clear. They imply the tLog can span events that happened BEFORE the
previous full backup! Basically I jsut want to kick out all users and do the
most simple type of backup that can easily be restored.
I tried to find docs related to this on Microsoft, but when I used the word
"migration" it came up with migrating from other Vendors, as opposed to
migrating to new hardware.
--
Gerry Hickman
SSRU SysAdminGerry
1) Search on internet for two stored procedures ('sp_help_revlogin')provided
by MS to move logins with their original SID
2) If you have jobs on the old server ,so script them as a later you will be
ran it the new one.
3) BACKUP all user databases and RESTORE them on the new ONE.Make sure that
you have the same path for the .mdf,.ldf files otherwise you will use
WITH MOVE option
http://vyaskn.tripod.com/moving_sql_server.htm
"Gerry Hickman" <gerry1uk@.netscape.net> wrote in message
news:u7dZfpVMGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I have 12 databases running on SQL Server 2000 on Windows 2000, and would
> like to move them all to new hardware comprising Windows Server 2003
> running
> SQL Server 2000. I already have SQL Server installed on the new box. In
> theory it's simple, but I have some questions:
> 1. Database security, logins, ownership etc; I hope to give the new server
> the same name as the old server but it will have a different SID and I
> don't
> know if there are any issues with that?
> 2. Merely restoring "user" databases to the new server means I will lose
> all
> kinds of useful configuration data such as my record of backups? Do I also
> have to restore Master, Model, MSDB, tempDB?
> 3. Is it best to detach/attach, or use backup/restore? If I use
> backup/restore I'm confused about the tLog restore. I used to think if you
> made a "full" backup you didn't need a tLog, but now I'm not sure, and the
> SQL Server Books on-line example of using tLog backup and restore seems
> far
> from clear. They imply the tLog can span events that happened BEFORE the
> previous full backup! Basically I jsut want to kick out all users and do
> the
> most simple type of backup that can easily be restored.
> I tried to find docs related to this on Microsoft, but when I used the
> word
> "migration" it came up with migrating from other Vendors, as opposed to
> migrating to new hardware.
> --
> Gerry Hickman
> SSRU SysAdmin
>