Jump to content

Recommended Posts

Posted (edited)

Mostly the issue of ESS stating you should use SQL 2016 and on the technical road map it classed as not supported:

 

Capture.PNG

Edited by willtech
Posted
Mostly the issue of ESS stating you should use SQL 2016 and on the technical road map it classed as not supported:

 

[ATTACH=CONFIG]65214[/ATTACH]

 

Yeah. I have seen that - But i was wondering if anyone has ignored there roadmap and carried on regardless?

Posted
Yeah. I have seen that - But i was wondering if anyone has ignored there roadmap and carried on regardless?

 

We went SQL 2016 played it safe. We did not want to play the risk of support refusing us support.

Posted

I wouldn't risk it personally. You'll have to run in compatibility mode anyway & if they see it after you've logged any issues they're within their rights to tell you to get lost.

 

It annoys me as well, as I feel like I'm keeping old OS's and SQL software around.

Posted
We had a third-party support company accidentally install it on SQL 2019 and even in compatibility mode we later saw issues which cost a third party several thousand pounds to get Capita/ESS to restore our database back to a new 2016 instance. Don’t do it it’s not worth it.
Posted
If you're using their built in transfer tools as well you'll find that it won't pick up the database to transfer to unless it's *exactly* the same version as your existing DB setup. We found this out when we migrated our SIMS server a few years ago.

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...