I've run into a few issues where a developer may have unintentionally created a stored procedure that hits a table twice for the same info. Usually, this is due to logic in the procedure and it's not that hard of a fix once it's found.
If I have the query I can go with SET STATISTICS IO ON and see the double work, but what if you don't have the query to start with.
One way I've gone about it is by using profiler to capture the scans and then drilling down from there.
Does anyone know of other ways to track down stored procedures using profiler that may be doing double work?