We are trying to pinpoint physical server performance issues hosting a SQL Server. I have been told by our IT team that there are settings for monitoring SQL Server system performance impact in Paessler and wanted to get more information.
One issue we have seen is errors come up in SQL replication to indicate that on large data transfers, the physical memory gets used to between 90 and 100%. What settings can be utilized in Paessler to track RAM usage per application?
Issue 2, we are getting pegged disk read queue length readings on this same SQL Server though we don't see identifiable SQL processes being run. What setting(s) would we need to set up to find where the io is being used and what server processes are running during the spike periods? This is a very high use, business critical server so we have hesitated running Performance Monitor traces. Can Paessler be set up to collect data without affecting performance?
Hello,
thank you very much for your interest in our PRTG Network Monitor. However, please bear in mind, that PRTG more offers 'basic' SQL-Monitoring options with its SQL-Sensors. If your SQL-Server runs on a Windows Machine, you might also be able to collect certain performance statistics using WMI (WMI Process Sensors for example), but it might not be a full SQL-Performance monitoring. Please also see:
Best Regards.
Mar, 2011 - Permalink