glad you're all sorted 😉

can only be done for adding columns as far as i know

Rod at work (7/17/2008)

---

We've got a new server purposed to be our new production database server. The system administrator would like to put VMware onto this machine and run...

you should always rename the server before SQL is installed.

Un install SQL server, rename the server then re install

virtual server enterprise will quite happily allow virtual sql servers to run, in fact it is possible to set up a 2 node sql cluster 😉

under 10 user connections!

i would home on an existing instance

have the backup verify the files at backup time. if storing on a backup on a network,

backup to local drive first then copy to network

when you attach\restore a db to SQL2005, i'm pretty sure it runs DBCC CHECKDB as part of the upgrade!

You would certainly be advised to update the stats to sql2005 stats

you can also use the alter database modify file command to move the files, make sure they're in the same location as MASTER as already stated

for future reference;

once the database is marked offline you do not need to detach the database you can just go ahead and copy the files...

go into Add\remove programs and select the .NET 2 framework. Run a repair of this first (click change\remove and it will ask to repair or remove)

as mentioned the primary reason for filegroups is to spread the database across multiple disks\arrays to increase performance. Placing filegroups on the same array is really pointless

just out of interest why are you upgrading Windows 2003 std to 2003 Enterprise in the first place. I always prefer a clean install for NOS's

presumably you have the ESX server installed\configured\secured and hooked up to the SAN?

sort of makes MSCS redundant really doesnt it