Unable to get Disk avg. read/write time for certain drives
avibooks
Posts: 15
Hi there,
We are using SQL Monitor on our production SQL cluster and after installing windows updates and restarting the SQL cluster, we are unable to get certain disk statistics for some of our drives.
I am able to get the performance counters for Disk avg. read/write time using Performance monitor on the server where the base monitor is located (using the login used by the Base monitor to connect to the SQL cluster), but SQL Monitor is not displaying the disk counters.
For some drives SQL monitor is displaying the Disk avg. read time but not the Disk avg. write time counter; for others its not displaying either counters; and for the rest it is displaying both counters correctly.
Could we please try and determine what is causing this issue as I see there was a similar ticket opened in Feb 2014 with no resolution.
Thanks and Regards,
Avinash
We are using SQL Monitor on our production SQL cluster and after installing windows updates and restarting the SQL cluster, we are unable to get certain disk statistics for some of our drives.
I am able to get the performance counters for Disk avg. read/write time using Performance monitor on the server where the base monitor is located (using the login used by the Base monitor to connect to the SQL cluster), but SQL Monitor is not displaying the disk counters.
For some drives SQL monitor is displaying the Disk avg. read time but not the Disk avg. write time counter; for others its not displaying either counters; and for the rest it is displaying both counters correctly.
Could we please try and determine what is causing this issue as I see there was a similar ticket opened in Feb 2014 with no resolution.
Thanks and Regards,
Avinash
Comments
https://documentation.red-gate.com/page ... d=20743048
Thanks for your response. I have just emailed support@red-gate.com with the attached log files.
Regards,
Avinash
I am reasonably confident that you are hitting a known bug, logged as SRP-9314 in our system. Unfortunately, I cannot say when the development team are going to be able to address it, but I have added all the information that you have given me. Hopefully they will be able to do something about it when they do.
Thanks for that. Is there currently any workaround for this bug?
Regards,
Avinash