i always favour migrating to a clean install rather than upgrade existing instances

have you tried re running the patch? it'll tell if if its already installed, might be worth re applying if you can

am i correct in saying you want to remove the extra filegroup and extra log file?

to remove the filegroup all objects in that filegroup would need to be moved to...

the 64 bit database backend should be transparent to the apps. SQL is SQL.

However check with the vendor that their app supports sql2005 as a database platform

use the SP_Addumpdevice stored proc, syntax is as follows

'type', 'device name', 'drive:\path\file'

type is either disk or tape

device name is the logical name you want to use

drive:\path\file should be self explanatory

which apps in particular?

use this handy script to change object owner to another user for objects ion the database

select 'exec sp_changeobjectowner '''+user_name(Uid)+'.'+name+''','' ''' /*owner to assign to, dbo for example*/

from sysobjects

where user_name(uid) <>...

search this site for some of Brad McGhee's tutorials, they're very helpful

as a side note BOL also recommends to update usages too using

dbcc updateusage

I've already seen a similar problem on a couple of databases i upgraded recently.

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