• The seek count and other extracts were not correct though for which I used...

    @arunleoprakash, our queries are looking for different things. The ScanCount column in my query tells you the number of times that a scan operation on the index appears in the query plan. If a plan only has one scan on your index, then the count will always show 1, even if the plan has been executed many times and your index has been scanned many times. When looking for total times a scan/seek/update has occurred, then yes your query is the right approach.

    My reasoning for including it is that if you get -- for example -- a scan count of 3 for some query plan, then you know you need to look for 3 places in that query/procedure if you want to find all instances of it.