Jump to content

[SIMS] Anyone running SQL 2019 now it's supported?


Recommended Posts

Posted

As per the title, is anyone running SIMS on SQL 2019 now it's supported?

 

ESS have no documentation/advice on SQL 2019 configuration and just point towards the 2016 docs. We have found that using 2012 compatibility mode can ruin performance on some schools and that potentially 2016 compatibility is optimal. It's most notable when running reports, we're talking 10-15mins for a super basic report, down to 5 seconds.

 

We're pushing ESS for a response and some official advice on this but I just wanted to gauge whether anyone else had experienced issues and/or been testing.

 

I read a post from jmcdermott last year that referenced 2016 compatibility but nothing since then. Seeing as all official advice until now has been to stick with 2012 mode, it seems odd that 2016 is now the flavour of the month.

Posted
If you can do it as a new server (spin up a VM, install SQL 2019, disable connections to old DB, copy DB over and attach it with the proper routines, test connection to it) then go for it. This would need to be done out of hours, with the backup of being able to switch back to the old server if it goes wrong! I did similar using Hyper-V snapshots to upgrade the existing server (which is obviously much easier!) which seemed a bit risky but it worked perfectly when I rolled back.
Posted
I would only bother doing this if you actually benefit from it - If they are just going to run in 2012 compatibility mode forever then I'm not sure what performance improvements you'll really get.
Posted
As per the title, is anyone running SIMS on SQL 2019 now it's supported?

 

ESS have no documentation/advice on SQL 2019 configuration and just point towards the 2016 docs. We have found that using 2012 compatibility mode can ruin performance on some schools and that potentially 2016 compatibility is optimal. It's most notable when running reports, we're talking 10-15mins for a super basic report, down to 5 seconds.

 

We're pushing ESS for a response and some official advice on this but I just wanted to gauge whether anyone else had experienced issues and/or been testing.

 

I read a post from jmcdermott last year that referenced 2016 compatibility but nothing since then. Seeing as all official advice until now has been to stick with 2012 mode, it seems odd that 2016 is now the flavour of the month.

 

The latest roadmap (Dec 2022) made reference to it: https://customer.support-ess.com/sys_attachment.do?sys_id=961b849d1b3925540f7143b6b04bcb8f

 

Screenshot 2023-09-15 083446.png

Posted
Didn't spot that bit of text Willtech so thanks for that. I do wonder if it was just a copy and paste though rather than a thorough test of what works well. We have a mixture of schools using SQL2019 on 2012 compatibility and others on 2016 compatibility as it made a huge difference to performance. Will report back once we get an official response from ESS.
  • 3 weeks later...
Posted
We've had a secondary school move to a new server in the summer. We installed SQL 2019 and the compatibility is set to 2012. They're are having nightmares with reporting. Some reports are taking 45 minutes. After reading this I'm going to try and change the compatibility to 2016 and try the report again.
Posted
We've had a secondary school move to a new server in the summer. We installed SQL 2019 and the compatibility is set to 2012. They're are having nightmares with reporting. Some reports are taking 45 minutes. After reading this I'm going to try and change the compatibility to 2016 and try the report again.

 

Hope it does the trick! Let me know how you get on.

  • 2 weeks later...
Posted

Hi Damon,

 

This didn't fix the issue for us. I've had to change it back to 2012 as changing it to 2016 started to disrupt other 3rd party SIMS addon's.

  • 9 months later...
Posted

Is there any update on this?

 

I migrated our DB over to SQL 2022 yesterday as it is now supported, but the DB is still in 2012 compatibility mode. The migration document doesn't mention whether we should now raise that to 2016 or 2022. Any ideas?

Posted

Just in-place upgraded from SQL 2014 to 2022 with no issues, didn't fancy rebuilding a new server with the amount of 3rd party apps, tools and custom tweaks to the server.

 

No issues if done right [emoji106]

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