Skip to Content

DB collector and SQL statement history in DBACockpit

Hi experts,

   I monitor our SAP system recently and I find there is probably an expensive SQL statement there.

I try to use SQL statement history but the physical reads data is not very high as I expected. What's wrong?

Is there any other DMVs and extended events I should check?

15,245 nuber of physical reads per second at 17:00 ~ 17:20.

Physical reads from 17:00 ~ 17:20 is just 1.1 millions which is not very high(ex: 60M)

sql1.png (50.6 kB)
sql2.png (67.8 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Nov 28, 2013 at 01:03 PM

    Hi Lee

    Kindly refer the link



    Add comment
    10|10000 characters needed characters exceeded

    • Hi SS,

         Thanks, I have already viewed all Leslie's presentations. I think she does not talk how to troubleshoot performance issue in detail.

         Anyway, I ask the same question in MSDN and I find I can Extended Events - Expensive Queries to trace.