I need to move an entire SQL Server installation (databases, logins,
replication, jobs, DTS etc) to a new physical server.

What method requires the least manual intervention? Ideally I would like to
not have to reenter user passwords, and the replication to pick up with the
remote SQL Servers where it left off etc.

If I restored master, distribution, msdb and all user databases to the new
server, would that recreate the entire state of the SQL Server installation?
Would I also need to rename the new server with the old server's name?

Hi Laurence,

It might be ful to check out :
http://vyaskn.tripod.com/moving_sql_server.htm

Nathan H. Omukwenyi, MVP [SQL Server]

"Laurence Neville" <laurenceneville@hotmail.com> wrote in message
news:OdQe7zm5GHA.3452@TK2MSFTNGP05.phx.gbl...
>I need to move an entire SQL Server installation (databases, logins,
>replication, jobs, DTS etc) to a new physical server.
>
> What method requires the least manual intervention? Ideally I would like
> to not have to reenter user passwords, and the replication to pick up with
> the remote SQL Servers where it left off etc.
>
> If I restored master, distribution, msdb and all user databases to the new
> server, would that recreate the entire state of the SQL Server
> installation? Would I also need to rename the new server with the old
> server's name?
>

I'd also recommend Vyas's reference for the general properties.
Replicationwise, you must have the same servername, or else you'll need to
script out the replication setup, change the references to the server name,
apply the scripts and then initialize the subscribers. If you can name the
new box with the netbios name of the old one before installing SQL Server
and restoring the databases, you should be fine. For this to work, you'll
need to stop replication and take the old server off the domain (or rename
it).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Thanks for both of your replies. I read the article and understand the
technique.

The only thing I am concerned about is where Vyas says "Install the exact
same version of Windows operating system on the new server.". My old server
is Windows 2000 and the new one is Windows 2003. Is it really critical that
the Windows versions are identical? What effect could the Windows version
have within SQL Server?

Thanks

"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:%23psVtas5GHA.3592@TK2MSFTNGP05.phx.gbl...
> I'd also recommend Vyas's reference for the general properties.
> Replicationwise, you must have the same servername, or else you'll need to
> script out the replication setup, change the references to the server
> name, apply the scripts and then initialize the subscribers. If you can
> name the new box with the netbios name of the old one before installing
> SQL Server and restoring the databases, you should be fine. For this to
> work, you'll need to stop replication and take the old server off the
> domain (or rename it).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>

My guess is that he is referring to memory/processor settings which are
restricted by the windows installation. These are partially configured in
the master database using sp_configure, and if you are restoring the master
database there'll be some dependency there. Alternatively, he might have
been referring to MS DTC (used in immediate updating subscribers for
replication) or windows firewall settings if these defaults are different on
different windows versions.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .