Finally we replaced our Test server.

A previous post outlined part of the discussion involved and the seriously twisted suggestion that a simple file copy of the entire data directory would be all that was required to bring the DBMS back up to its original state.

Although I am sure that other people have done this, I would like to enter the phrase "Crazy George" as the term for this method in honor of the lunatic DBA who suggested, tested and finally proved to us that it worked.

Process:

The boxes where different - More and faster processors, more RAM, better disks etc..and the OS on the new box was a Service Pack ahead...

• Installed Windows OS on a new box and gave it the same name as the old box (off network)
• Installed SQL Server with same Service Packs as old box and ensured that the default data directory was the same as well and then stopped SQL Server and all its related services. DTC, Search, Agent etc...
• Copied the entire data directory (effectively a whole logical drive) from the old box to the new box giving us an identical copy.
• Removed the old box from the network and added in the new box.
• Started SQL Server

It worked perfectly except for 1 small problem - The DBMS was telling us that the Full Text catalogs where empty or not populated. Issuing the RebuildAll command from EM, brought the catalogs backup instantly with a status of Fully Populated.
All Jobs, DTS packages, Security settings (including Linked Servers) where maintained and according to the users/developers , the only difference now is the speed!.
Unfortunately, there was no replication on the box, so I cannot report on that..

The file copy was the longest part being about 2 hours and the rest of the process took about 30 minutes.

From the initial post, there was only one negative response to this method, although the reasons given where not of the highest quality (ie None). Its a brand new day Neil.