Restoring databases

This weekend I have to restore a backup from one SQL server 2000 machine to
another. I am doing this simply because we are updating the hardware, so
when the new machine has been built it will have the same network name as
the original box. The current box is running Windows 2000 Server with SQL
2000 sp2, the new box will be Windows 2003 and SQL 2000 sp3a. There are 8
small databases totaling 1.5Gb. My question is do I need to restore any of
the SQL databases? msdb? pubs? I normally do this for SAP databases where I
only have to restore the SAP database and nothing else. Can anbody enlighten
me?
GavYou don't actually need to restore any of you system
databases unless you have modified or added code in them
(which is a bit dangeous anyway).
In your text you said the pubs database, thats not a
system database but a user database, the answer is it
depends if you have changed it.
BTW the best way of doing it is not to restore them, but
to detach the database and copy over the log and data file
onto the new server then re-attach them. It will save you
a bit of time ;)
Peter
"Adam and Eve had many advantages but the principal one
was that they escaped teething."
Mark Twain
>--Original Message--
>This weekend I have to restore a backup from one SQL
server 2000 machine to
>another. I am doing this simply because we are updating
the hardware, so
>when the new machine has been built it will have the same
network name as
>the original box. The current box is running Windows 2000
Server with SQL
>2000 sp2, the new box will be Windows 2003 and SQL 2000
sp3a. There are 8
>small databases totaling 1.5Gb. My question is do I need
to restore any of
>the SQL databases? msdb? pubs? I normally do this for SAP
databases where I
>only have to restore the SAP database and nothing else.
Can anbody enlighten
>me?
>Gav
>
>.
>|||"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:2f1d01c520d6$32bc7970$a501280a@.phx.gbl...
> You don't actually need to restore any of you system
> databases unless you have modified or added code in them
> (which is a bit dangeous anyway).
> In your text you said the pubs database, thats not a
> system database but a user database, the answer is it
> depends if you have changed it.
> BTW the best way of doing it is not to restore them, but
> to detach the database and copy over the log and data file
> onto the new server then re-attach them. It will save you
> a bit of time ;)
> Peter
> "Adam and Eve had many advantages but the principal one
> was that they escaped teething."
> Mark Twain
>
> >--Original Message--
> >This weekend I have to restore a backup from one SQL
> server 2000 machine to
> >another. I am doing this simply because we are updating
> the hardware, so
> >when the new machine has been built it will have the same
> network name as
> >the original box. The current box is running Windows 2000
> Server with SQL
> >2000 sp2, the new box will be Windows 2003 and SQL 2000
> sp3a. There are 8
> >small databases totaling 1.5Gb. My question is do I need
> to restore any of
> >the SQL databases? msdb? pubs? I normally do this for SAP
> databases where I
> >only have to restore the SAP database and nothing else.
> Can anbody enlighten
> >me?
> >
> >Gav
> >
> >
> >.
> >
What about any users that are defined in Logins? Where are they stored?
Thought about detaching the databases but they are on local storage and both
machines have the same name so without changing server names we cannot have
them both on the network at the same time. Restore takes no time at all so
its probably less hassle.
Just read up on the other databases, doh, didn't realise pub was just a
sample like northwind. :o)
Gav