SIMS SQL Compatibility mode

[Sheridan]

We're having lots of issues with Wonde and Classcharts writebacks, delays and just running for long periods. Their solution is to set our SIMS SQL to 2012 Compatibility mode which seems like a backward step

 

The SQL is currently 2016 and is running on a well overspecced server so its not a resource issue

 

Has anyone else done this, it seems like a strange request? Its not something I would change on a live server during working hours anyway but I'm not sure what impact it will have just switching it from 2016 to 2012 mode (and why not 2014 mode!?)

[Boredguy]

It's always been a case that it needs to be in 2012 compatibility mode, even if you are running the latest version of SQL server.

 

Due to how it was designed it's likely that the bulk of SIMS .net is still using the same framework as it was back in the Capita days, as it would cost more to try and update all the modules/nova-T etc when the new owners are ploughing ahead with their Next Gen modules.

[Sheridan]

I wonder if changing it on an existing system (I inherited this) from 2016 to 2012 will cause any issues - last thing I need is a corrupt SIMS DB!

[Boredguy]

Shouldn't cause any issue as it is something the support companies have done on our it trust SIMS installations soon as we had them upgrade from SQL 2014 to 2019 (or 2022 which we should be getting done this summer)

[Sheridan]

Its funny, as I looked after SIMS at a previous job for 15 years and never changed it (probably was 2008/2012 or earlier back then) and I've never had to check here until now!