This would also be a good time to document your Disaster Recovery plan.

Me? I would install the same OS and SQL versions on the new machine,
offline, using the old names AND locations for everything. Then I would
do a complete backup of the SQL server, not just the data, from the old
server, then restore that to the new server. Offline the old server,
reboot and online the new server. Viola! down time should only be the
time it takes to run the backup and then the restore/reboot.

Good luck.

Dan





I'm looking for the best overall SQL Server hardware upgrade
methodology. We need to move an instance of SQL Server from an old
server to a new one with minimal downtime. However, due to limitations
of our third party software which uses the SQL Server as a back-end,
both the server name and instance name must be the same on the new
server. Everything must be copied over, from security, views and stored
procedures to backup schedules and replication configuration.

I've read about several different approaches for doing this, but none of
them are very simple. I'm looking for the LAZY (as in LazyDBA) way.

What is the most acceptable way to do this?

Michael Phillips
Cardiac Science
[Email address protected]


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html




MS Sql Server LazyDBA home page