Index Searches/Sec

  • Hello,

    I recently had a performance issue where CPU flat lined at %100 severely degrading performance.

    When reviewing the daily Perfmon counters I collect it was clear at the time of the incident when Processor Time spiked so did Index Searches/Sec.

    My question is can I find out after the incident which index was the one being heavily utilized?

    If it's not possible post-incident is there a quick way to find out during, in case it happens again :\

    I'm hoping by finding the index, I can work backwards and find the offending query.

    Thanks,

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply