Rebuilding Sql Server 2000 from Backups

I am trying to rebuild our server onto another - which will have the
different name.
So I expect the best way to handle this is to just do a backup on the old
server for each database and then restore them on the new server.
If I go this way do I need to:
1. Create the database first and then do the restore for each database?
2. Re-add the Logons (since the database will have permissions set for these
logons). And do I need to create the logons before doing the restores?
3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
will that be taken care of as I restore the databases?
Thanks,
Tom
On Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> I am trying to rebuild our server onto another - which will have the
> different name.
> So I expect the best way to handle this is to just do a backup on the old
> server for each database and then restore them on the new server.
> If I go this way do I need to:
> 1. Create the database first and then do the restore for each database?
> 2. Re-add the Logons (since the database will have permissions set for these
> logons). And do I need to create the logons before doing the restores?
> 3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
> will that be taken care of as I restore the databases?
> Thanks,
> Tom
1. You don't need to create the databases first. Just restore
database will do what you need.
2. You are going to fix the users. If you're going to add teh logins
to the new server you will have something called orpaned users. Take
a look at the Books On Line and read the sp_change_users_login proc
since you will use it to fix the user issue. Of once you restore the
database to new server just delete the user, add the login and add the
user to database.
3. If you don't have a lot of jobs and dts packages I would generate a
sql script for jobs then run them on the new server and just save the
dts packages once you get the new server up to that server. Don't
wory about model it's just model db to create a new database. Leave
the master and msdb out of the process.
Good day,
Bulent
|||"Bulent" <bulentgucuk@.gmail.com> wrote in message
news:1177033048.966489.192990@.b75g2000hsg.googlegr oups.com...
> On Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> 1. You don't need to create the databases first. Just restore
> database will do what you need.
> 2. You are going to fix the users. If you're going to add teh logins
> to the new server you will have something called orpaned users. Take
> a look at the Books On Line and read the sp_change_users_login proc
> since you will use it to fix the user issue. Of once you restore the
> database to new server just delete the user, add the login and add the
> user to database.
> 3. If you don't have a lot of jobs and dts packages I would generate a
> sql script for jobs then run them on the new server and just save the
> dts packages once you get the new server up to that server. Don't
> wory about model it's just model db to create a new database. Leave
> the master and msdb out of the process.
I was wondering about the restore process if the Database was not there as
it is not in the list of databases to restore, which makes sense it isn't
there. But you can add the name in the list and it works fine, as you said.
Thanks,
Tom

> Good day,
> Bulent
>