Sims SQL upgrade 2008 R2?

[zag]

Can I use SQL server 2008 R2 in the upgrade process for Sims from 2005 version?

[bodminman]

IIRC the guidelines tell you this. The answer is though I don't think so.

[Theblacksheep]

We were advised not to use sql2008r2.

 

2008 only.

[FN-GM]

We were advised not to use sql2008r2.

 

2008 only.

 

Same here.

[zag]

Grr I wish Capita would keep up-to-date.

 

I've checked the install notes and there is no mention about not using SQL server R2 in there.

[cl0n3]

I used SQL2008 SR2 in the upgrade process and haven't come accross any issues (or no more issues than usual) Edited October 26, 2010 by cl0n3
missed the L in SQL2008

[Theblacksheep]

Grr I wish Capita would keep up-to-date.

 

I've checked the install notes and there is no mention about not using SQL server R2 in there.

 

FYI: Our was a call from the LA (last month) saying "you've not used 2008 r2 have you? theres been some backend issues discovered and 2008 must be used"

[Arthur]

I was advised against this by Capita too (yesterday in fact). I wonder if the delay is due to Microsoft's .Net Framework v1.1 not being supported on Windows Server 2008 R2?

[zag]

Got this error during the migrate process, any ideas how to fix?

 

 

EDIT: Nevermind, carried on with the manual steps and its working ok.

 

How do I set the recovery model?

Edited October 26, 2010 by zag

[matt40k]

Have you got SQL Management studio installed?

[zag]

Yes I have, (I just used it to give the backupexec user permissions to connect to the DB) Edited October 26, 2010 by zag

[localzuk]

The key question here is - why do you want to use SQL2008 R2 when Capita say not to?

 

Surely you should use the tools that Capita state are the right ones?

[matt40k]

Grr I wish Capita would keep up-to-date.

I've checked the install notes and there is no mention about not using SQL server R2 in there.

 

Maybe because the document was written pre-SQL2008R2. Distribution of updates isn't as easy as you think.

 

I was advised against this by Capita too (yesterday in fact). I wonder if the delay is due to Microsoft's .Net Framework v1.1 not being supported on Windows Server 2008 R2?

 

SIMS uses v2, it's moving to v4 in Spring 2011. Not aware of anything using v1.1, I guess there is some small bit in there that could be.

 

How do I set the recovery model?

 

Database > properties > options > recovery model - change to simple. If you can't figure it out, close sql studio management and log a call with capita\local support team and request the patch.

 

The key question here is - why do you want to use SQL2008 R2 when Capita say not to?

Surely you should use the tools that Capita state are the right ones?

 

I agree. Only reason I can think of is if your trying to save money buy SQL 2008 standard (and your database is over 4GB).