Install SQL 2005 Full over 2005 Express (other instances)

[Heebeejeebee]

Hi,

 

I'm looking for a bit of advice and reassurance.

 

I'm just wondering if there will be any problems upgrading SQL 2005 Express to full SQL 2005 for our SIMS server if there is another piece of software using SQL Express as well. We have Schools Cash Office & Lettings software (BPR Solutions) that shares the same server. Both SIMS and the BPR Solutions packages show in the SQL Server Service Manager.

 

Will they both move over or can I select just to migrate SIMS? I don't want to start on this in case it all goes pear shaped because of this and I get to a point of no return before I find out.

 

Looking thorough the SIMS documentation for upgrading it suggests that you can move just the SIMS database over but doesn't say if full SQL and Express will work happily together. I suspect they will but would like confirmation.

 

Cheers

 

HBJB

[timzim]

The upgrade process should find all your current instances and ask you if you want to upgrade them. Run the SQL install from the command line and use the SKUUPGRADE=1 switch (e.g. d:\setup.exe SKUUPGRADE=1).

[Heebeejeebee]

Cheers,

 

If I decline the update it'll still work with 2005 Express then (?). My main concern is that the one that I want left alone will be borked up.

 

HBJB

[matt40k]

Depends, I assume you have two instances of MSSQL, ie two copies. I think if you do it write it should be ok as they are independ. I'm not sure tho, so I would defo make a full system backup first.

 

Maybe make a VM image of the server then try it on the VM first.

[timzim]

If I decline the update it'll still work with 2005 Express then (?). My main concern is that the one that I want left alone will be borked up.

 

Not sure you can have two different editions of SQL 2005 on the same machine. You'll get more functionality (and won't lose any) with Standard Edition than with Express so you might as well upgrade all your instances. See here for more details. As long as you do a thorough backup first (and/or run on a test server as suggested above) you shouldn't have a problem.