[sims] [SIMS] New SIMS server for July 2013

[AJWhite1970]

Hi

 

Just about to build a new SIMS server ready for a migration from W2K3/SQL2008 in early July 2013.

 

Just wondering what versions I should build the server given current support levels from Capita....

 

A) Windows 2008R2 with SQL 2008

B) Windows 2008R2 with SQL 2012

C) Windows 2012 with SQL 2008 (and then update at a later date to SQL 2012)

D) Windows 2012 with SQL 2012

 

I would like to go with Option D but is Option C safer until the Summer 2013 update and 47 hotfix patches are released first?

 

TIA

Andrew

[Rawns]

Hi

 

Just about to build a new SIMS server ready for a migration from W2K3/SQL2008 in early July 2013.

 

Just wondering what versions I should build the server given current support levels from Capita....

 

A) Windows 2008R2 with SQL 2008

B) Windows 2008R2 with SQL 2012

C) Windows 2012 with SQL 2008 (and then update at a later date to SQL 2012)

D) Windows 2012 with SQL 2012

 

I would like to go with Option D but is Option C safer until the Summer 2013 update and 47 hotfix patches are released first?

 

TIA

Andrew

 

D) is fine providing you do not use SOLUS3 or SIMS Discover.

 

If you do use them, I'd go for C) and then migrate SIMS, FMS, SOLUS3 and SIMS Discover over to SQL2012 after the Summer release when they will all be supported and the Capita migration tools are avaiable.

[FN-GM]

If you go option A or C dont use SQL 2008 use SQL 2008 R2

[AJWhite1970]

Thanks for the advice. It confirms what I suspected, start with option C and upgrade SQL over Christmas :-)

 

Cheers

Andrew

[AJWhite1970]

@FN-GM Thanks. I did mean SQL 2008 R2 but still in the habit of just typing SQL2008 even after all these years.....

[synaesthesia]

So why not do it all 2012 in the first place and save the hassle? (we're testing this currently on server 2012 and SQL 2012.). Can't see the issue as Summer release supports both, including Discover and Solus 3.6, especially if on a new server.

[Rawns]

So why not do it all 2012 in the first place and save the hassle? (we're testing this currently on server 2012 and SQL 2012.). Can't see the issue as Summer release supports both, including Discover and Solus 3.6, especially if on a new server.

 

Because if he does use Discover and SOLUS3 (which I get the impression he does), they will not work on SQL2012.

Edited June 4, 2013 by Rawns

[synaesthesia]

they do in the summer release (this time next month)... so what's the issue?

 

Delay the migration until the summer itself, give capita enough time to fix what will certainly be one or three broken releases and do it all in one go without doing it again at Christmas.

[Sylv3r]

I'm going with Option D as soon as the Summer release has been released.

[AJWhite1970]

Morning all.

 

Normally I would agree with you all and go for option D, but I have a very small upgrade window available right on the projected date of the Summer release so will air on the side of caution just this once, install with Option C and install SQL2012 either October half term or Christmas.

 

Thanks for all the replies

Andrew

[Boredguy]

We've gone for Windows 2012 and SQL 2008 R2 for now since SLG and discover won't work on SQL 2012 until September according to the migration team, and means I can save getting the SQL 2012 licence until next FY.