[sims] Nova T4 Reports to slow in SIMS

[CatherineMay]

Hi Guys, I am frustrated with the reports in SIMS!!!!! To call up a teacher/student timetable is so slow, I could run round and look in every rooms before the timetable appearing in screen!!! Anybody else having the same problem.

[localzuk]

It just took me 3 clicks to bring up a timetable for a teacher here, with about 5 seconds waiting whilst it churned away.

 

Repeated this with a pupil, and again, 3 clicks, less time processing.

 

How are you pulling the reports up? I assume you are referring to Reports -> Timetables -> Staff/Student timetables?

 

What stage is taking so long?

[CatherineMay]

Yes I am referring to Reports -> Timetables -> Staff/Student timetables, the first screen appears immediatley,select the person I want, and wait, wait wait and wait!!!!

[localzuk]

That sounds like your SIMS server is not up to the job. Can you provide us with the following details?

 

Database size (the .mdf file size):

Spec of the server (CPU/RAM and whether you have the OS on a different drive array to the database files):

Which version of SQL Server you're running (Express or full):

Amount of memory that the sqlservr.exe process is using on the SIMS server:

 

Then we can advise as to where you need to make changes.

 

Our SIMS server here is an Operton 2Ghz dual core system, running 3GB RAM, with SQL Express and a database of just over 1GB in size. The sqlservr process uses about 1.2GB RAM and we have zero issues with slowdowns like you describe.

[CatherineMay]

Thanks for that, I will ask the IT System Manager for the specs and get back to you.

[BatchFile]

This might also be a good time to request the database re-index patch from whoever you get your SIMS support from; that should make all your reporting activities run much faster.

[CatherineMay]

Already have the patch!

[bossman]

@CatherineMay:

 

Less than 3 seconds here, so I would conclude that it is either the database that needs re-indexing which has already been covered or as @loculzuk has mentioned your server is not up to the job.

 

We have it running as VM with only one CPU at the moment with 8Gb RAM looking at increasing the CPUs to at least 2 to see if it does make any difference.

[vikpaw]

When did this start? Is it all day everyday for a while?

If it's recent, it could just be someone is doing something that taxes the system, e.g. applying a timetable for next year, promotion or other such end of year task.

[m25man]

As stated, we need more system info to help with this one.

I have SIMs running on small servers with barely more power than a desktop and others with 8 cores and 64Gb of RAM

It all depends on what your trying to do with it.

 

RAM is your highest priority because with little RAM SQL will be thrashing the Disk I/O using the disk as Virtual RAM, if you have a slow disk subsystem and little RAM your in trouble.

Couple this to what @vikpaw says, background applications, file serving and AV could tax your system more than a Tory government in a recession...

 

Check your AV settings make sure your not on demand scanning every file open/close in your database and on your clients make sure your not AV scanning every file on your SIMs network drive/path. Your AV scanning overheads can cripple SIMs and other database applications.

[CatherineMay]

Thanks for all your replies. Everything is over my head. I have inserted below the email from our tech.

 

Hi Cath,

Database size (the .mdf file size): 3,097,088kb

Spec of the server: Dual Core Hyperthreaded Intel Xeon cpu 3.0ghz 4gb of ram

Which version of SQL Server you're running (Express or full):full SQL server 2008 EE

Amount of memory that the sqlservr.exe process is using on the SIMS server: 1,744,248kb

 

Cheers

Phil

 

Does that help?

 

[localzuk]

Its a little odd that the SQLServr.exe process is using so little RAM with a database of that size.

 

However, as a beginning point, I'd suggest getting your network manager to disable hyperthreading and then retry the timetable reports. Hyperthreading can cause big issues with SQL server. I have it disabled on our SQL Server machine for this reason. (This is done in the server bios).