Client Management Suite

Hello. Over the past couple of days the console has been getting worse and worse. Today it doesnt seem to display properly anymore. (see pic)

Event id 0

Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.

recently the SQL server has been changed from having 2 vcpu's to 4 vcpu's. This is on vmware.

today i have rebooted the altiris ds7.1 server and this hasnt seemed to help.

after some investigation i can see other databases on the same sql server that seem to be fighting for the disk activity.(see picture 2)

would a sql server with other databases fighting for survival cause this issues with the CMS.

on the CMS/NS server task manager is showing fine, normal memory/cpu usage.

Am I on the right path here? or could there be another factor ive not considered.

Any ideas?

Thanks.

You are certainly on the right path. When chasing down 'response' issues on the SMP, my first point of focus is the SQL instance. It doesn't matter how well tuned your SMP is if the data that it uses is being delayed by a choked SQL.

Aside from the normal SQL maintenance activities (reindex, backup, log file maint), you may need to revisit exactly what databases you have on that instance and how they are configured.

I notice that SolarWinds is sharing the same instance. SolarWinds (depending on what you are monitoring and how you are doing it) can understandably be a real 'chatterbox' in terms of SQL usage. If possible, consider either relocating the SolarWinds db to a seperate instance or at least a seperate physical array to try and alleviate  some of its IO load.

You also appear to have your tempdb on the same array as the other database files. While SMP7.1 has made huge steps in reducing the load it places on tempdb, there are still places that it is required. As the tempdb files are on the same array as the other db's, any db traffic that innundates the IO for that array is going to cause problems for tempdb usage. Consider relocating tempdb off to a faster array - away from the other db's.

Please find atatched PDF's with

- Best Practices...

- Maintenance Plan...

- And IOPS...

Have Fun!

Attachment(s)

Supplement-Creating_a_SQL_Maintenance_Plan.pdf   292 KB 1 version

Supplement-SQL_Implementation_Best_Practices_and_Optimiza...pdf   298 KB 1 version

Supplement-Understanding_IOPS.pdf   708 KB 1 version

Thank you very much for both of the replies. I am going to look over all this info provided and try get a working solution.