upgrading sims server from 2008 to 2016

[YCDCN]

Hi,

We are looking at upgrading our Sims server, has anyone got any useful info that we should know from past experiences?

[deano3693]

I would just build a new one - It's not that difficult as you are going to have to go from 2008 - 2012r2 and then upgrade again to 2016 so isn't very clean! You will also need to be running at least SQL2012 as SQL2008 isn't supported on 2016.

 

You will need to disable all the SQL Services before upgrading otherwise it will fail and roll back.

 

Other than that it should work fine but for cleanliness i would rebuild rather than upgrade.

[Sylv3r]

I would definitely recommend a new server and migrate the DB's over.

 

There's plenty guides on the SupportNet site on how to do it, or depending who you receive your SIMS support from, they'll be able to do it for you for a fee.

[FishCustard]

Another vote for 'build a new server'. It's really not hard to do, the annoying thing is that the last installable release is from 2013 so you'll have to sit through a bunch of database upgrades.

 

Also has the massive advantage of keeping the old server working until you're sure the migration has gone okay.

[pubgrub277]

Another vote for 'build a new server'. It's really not hard to do, the annoying thing is that the last installable release is from 2013 so you'll have to sit through a bunch of database upgrades.

 

Also has the massive advantage of keeping the old server working until you're sure the migration has gone okay.

 

No, that installable is only if you're starting from a blank DB as a new school.

 

Migrate you files (docstorage, STF folders etc) and the physical DB files to the new server. Attach using SQL management studio or the DBattach tool provided by Capita.

 

There are migration tools available from Capita, or a local support unit will probably do it for you if you ask.

[FishCustard]

No, that installable is only if you're starting from a blank DB as a new school.

 

Migrate you files (docstorage, STF folders etc) and the physical DB files to the new server. Attach using SQL management studio or the DBattach tool provided by Capita.

 

There are migration tools available from Capita, or a local support unit will probably do it for you if you ask.

 

Hmm interesting! Our LA support insisted that we needed to use the installable release for a migration, despite me questioning that! I'm not surprised that they don't know what they're talking about.