[sims] Slow "Edit Academic Year"

[Jawloms]

End of last week we edited our academic year to allow for yesterday's bank holiday. After 15 minutes of SIMS apparently applying it and no-one else being able to use SIMS we crashed it out. I then ran it on the server with no-one else connected Saturday morning. It took three hours! Anyone else or just us for some reason?

 

Stuart

[hellgate24]

Yes had exactly the same today. As soon as edit academic year is started it bombed SIMS for everyone else. In fairness it does say before you run it that it will take a long time. I ended up ditching it and adding the bank holiday through School Diary instead. Edited September 20, 2022 by hellgate24

[pete]

It took ~5 minutes when I did it at one of our secondaries a week or so ago (middle of a lesson period). Server isn't anything amazing (4 cpus allocated, 24G RAM, 18G SIMS db, ~840-ish students) but it didn't take any time.

 

3hrs on a Saturday isn't right and something's off there.

[Cat_Jam148]

Same issue here - going to have to logon tonight and give it another go

[ultima170387]

we added ours via the school diary and didnt use edit academic year as advised by our SIMS support provider - took seconds

[AnglianEdu]

I thought I was big and clever with this - I add a new academic year this lunchtime and it took about 30 minutes. Not too bad I thought.

 

I was then told that actually we had wrong date on our school term dates I have been provided so thought that since it only took 30 minutes to add the year, changing a single date should be quicker than that.

 

It's TWO AND HALF hours later and it's still running. How on earth can it take half an hour to add an academic year and so long to change a single date by one day? How long can I expect it to take?

 

Not very popular right now as a couple of our staff want to use SIMS and the screen says very clearly that edit academic year should not be interrupted!

Edited May 30, 2023 by AnglianEdu

[Jawloms]

Leave this to complete now you've started it, but in future try running the shrinkdblog thingy beforehand.