[sims] Upgrade SQL 2008 Express to FULL 2008 R2 Standard

[fiza]

I am about to upgrade our SIMS install from SQL Express to SQL Full prior to moving the whole lot to a new Server. Not being a SQL person I wanted to know if this will work for SIMS just by doing a normal upgrade of SQL. Do I have to do anything special with SIMS DB before doing the upgrade?

 

Any pitfalls or other things you guys can point out would be most welcome.

[zag]

I did this for sharepoint recently and it was a simple case of loading the 2008 R2 installer and clicking upgrade existing install.

 

Worked fine with all the permissions and stuff.

[NorthernSands]

If you're moving to a new SIMS Server, the DB will be quite happy to DB[un]Attach[ed] from the SQL Express instance and DB[re]Attach[ed] to the new instance on the new server. There's no need to upgrade SQL Express to Full before migrating.

 

It's often a good idea to leave the existing SIMS box as is when migrating to a new server; it becomes an absolute 'known good' in case things go apex-over-base.

 

What @zag says is perfectly correct if you're staying on the same box.

[fiza]

If you're moving to a new SIMS Server, the DB will be quite happy to DB[un]Attach[ed] from the SQL Express instance and DB[re]Attach[ed] to the new instance on the new server. There's no need to upgrade SQL Express to Full before migrating.

 

It's often a good idea to leave the existing SIMS box as is when migrating to a new server; it becomes an absolute 'known good' in case things go apex-over-base.

 

What @zag says is perfectly correct if you're staying on the same box.

 

The idea was to move to SQL Full on the current box as we are getting too big for SQL Express and users are getting frustrated with it and then migrate to the new box over the summer holidays.

[vikpaw]

I'd prefer to wait then move direct to a new box so you do have a working system as a backup.

 

If you do do it in situ, take db backups before hand of course, and ideally, run dbattach to detach the db and then reattach it to same server/version/instance, so all users / logins are stored in the db, should anything go crazy.

[jinnantonnixx]

I'd prefer to wait then move direct to a new box so you do have a working system as a backup.

 

If you do do it in situ, take db backups before hand of course, and ideally, run dbattach to detach the db and then reattach it to same server/version/instance, so all users / logins are stored in the db, should anything go crazy.

 

Excellent suggestion. Worst case is you keep using your existing (working!) system.

 

I've never liked the idea of in-situ upgrades (based on nothing more than bad experiences!!!), even though I'm sure these upgrades are tried and tested.

Edited May 10, 2011 by jinnantonnixx

[Edu-IT]

We are moving from SQL 2008 Express to either SQL 2008 or SQL 2008 R2. What would people recommend? Is SIMS okay on SQL2008 R2 now?

[Mcshammer_dj]

I would wait and move to SQL 2012

[superfletch]

I would wait and move to SQL 2012

 

Bang on - SQL2012 support is from the next upgrade for SIMS and FMS although you'll have to wait until September for Discover (unless you're using SOLUS 3 an on v 3.6)

[vikpaw]

Using SQL 2012 for some other services and it's nice. Even just the ease of closing down unused query windows is such a time saver especially when working remotely.