Jump to content

Recommended Posts

Posted

I know Server 2019 is not currently supported by Capita until Spring 2020, however is any one running Sims on Server 2019 already? If so have you had any issues?

 

It is our last major server migration before January and I want to standardize on 2019 (and I will be honest I don't want to set it up on 2016 only to move it again in March when Spring release drops). I have seen people have had issues with SQL Server 2017 / 19 and it looks as though they will only support SQL 2016 R2 for the significant future so was going to stick with that.

 

Our current server only has Sims, FMS and Solus 3.12.41 (plus couple of groupcall products).

Posted
I know Server 2019 is not currently supported by Capita until Spring 2020, however is any one running Sims on Server 2019 already? If so have you had any issues?

 

It is our last major server migration before January and I want to standardize on 2019 (and I will be honest I don't want to set it up on 2016 only to move it again in March when Spring release drops). I have seen people have had issues with SQL Server 2017 / 19 and it looks as though they will only support SQL 2016 R2 for the significant future so was going to stick with that.

 

Our current server only has Sims, FMS and Solus 3.12.41 (plus couple of groupcall products).

 

Nope we're on 2016 and will be until the next time we have to replace the server, as it was only replaced last year. I understand where you're coming from, but why make life harder for yourself? If 2019 isn't supported yet, that's the first thing they'll say?

Posted
We're on server 2019 since half term and touch wood it's been fine. It'll be a pain to go back - that said our migration was done by our sims support company and they didn't bat an eyelid about it being 2019...
  • 4 weeks later...
Posted

if you're capable of installing sims yourself and using the database migration tools then it's just your time and effort.

 

Our IT support company was upgrading all of our servers to server 2019 so that may have cost a few hundred quid and then our SIMS support company charged £600 for the database migration bit.

Posted
Its not that hard to do yourself. I have done 4 primary schools so far. Do a test migration on a virtual server first just to make sure everything will be OK.

 

The Solus3 migration is hard apparently. What’s your experience of that part?

Posted (edited)
The Solus3 migration is hard apparently. What’s your experience of that part?

 

I found it fine. I migrated Sims and FMS first then the following week migrated Solus3. There is no migration tool for Solus3, so I made a backup of the Solus3 database and then imported it into the new SQL version. Needed to make a couple of changes in the Solus GUI to let it know where the new database was and a couple other changes and that's it.

 

I did this first on a test vm, worked out the odd kink and all OK.

 

EDIT - The only issue I needed to workout was why all the clients listed in Solus3 where offline, but realised that in the Solus3 programs folder is a connection app, after typing in the new SQL info all clients listed as being online again.

Edited by TwistedHelixis

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...