You can also check msdb database table named suspect_pages for possible reasons if it's related to corruption.

https://msdn.microsoft.com/en-us/library/ms191301.aspx

MJ

Thanks everyone for your prompt replies:-)

I was mistakenly taking whole column density (0.000008815) into consideration rather than the predicate one (0.603061).

Predicate--> WHERE TH.TransactionID BETWEEN 100000...

Grant,

There are 113443 rows in this table and all rows are distinct rows but, I ma confused why optimizer estimated 68412.4 rows than 68412??

Thank you..

I am happy with the results provided by sql engine but, my question is how exactly this figure (estimated rows 68412.4) is derived.

Thanks,

Manu Jaidka

Jeff,

Stats were updated today itself with full scan. In fact, I downloaded this database today morning only.

Question strike me while reading http://sqlperformance.com/2014/01/sql-plan/cardinality-estimation-for-multiple-predicates

Thanks,

MJ