Problem when identifying expensive SQL using DB collector history

[former_member211576]

Hi experts,

   As you can see in screenshot 1, I find page life expectancy decreases less than 300 and IOPS increases to more than 1800 from 11:20.

However, physical reads are not increases accordingly in SQL statement history. What does this mean? Does IO come from external programs?

If so, what tool do you recommend to identify the cause? Management Data Warehouse?

[former_member211576 · Accepted solution]

Hi All,

   probably a bug?

http://support.microsoft.com/kb/2845380/en-us