It's not that difficult, but there are some gotchas that are not usually
mentioned in documentation. I've done it several times.
The most critical part is restoring the system databases (master and msdb).
Things to watch out for:
(1) It is MUCH easier if the SQL drive letters and directory structure on
the new machine are the same as the original machine.
When you restore the MASTER database, it will look for all of your database
files in the same physical locations as they were on your original machine.
If you don't keep the same structure, then email me, cause I've got some
steps you can follow.
(2) There is a special procedure to restore the MASTER database. You can
find it on the Microsoft knowledge base, or in SQL Server Books Online
documentation. Try the BOL first.
(3) Once the MASTER database is restored, your NEW server will possess the
identity of the OLD server. To correct this, and rename the SQL Server,
re-run the SQL Server installation from the installation CD. I think there
is a repair options, but either way, if you run the installation again, it
allows you to change the SQL server name, and it won't wipe out your
> Hello there,
> We are going to move the SQL server(NT4SP6a, IIS4, SQL7SP3) to a brand new
> server(NT4SP6a, IIS4, SQL7SP3). The new server name is different from the
> old server. There are microsoft project central server to run on the old
> How should I do to keep the PJC and other user database continue working
> when I move?
> Is there any documents to help me?
> any ideas?