March 9, 2009 at 6:31 am
Interesting question... I'm not sure it'll help, but you can get the actual logical and physical reads by query for the queries that are in cache using sys.dm_exec_query_stats. Generally I haven't measured performance by I/O on tables or indexes, but by I/O (and time & cpu) on the queries in question. If that I/O goes down, then naturally the other does.
However, that's clearly not directly answering your question. I'm not aware of a mechanism to get this per table. Per database through the Performance Monitor is possible and through trace events or querying the DMV mentioned above will work for queries. But I don't know a method for a table.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 9, 2009 at 7:09 am
Well, I feel a bit better. I spent a lot of time digging and couldn't find anything. I'll post the same question on usenet and see if any of the brains there come up with anything.
I agree, query reads are more useful, but sometimes reads at the table level are a useful high-level metric, too, and I'd like to know if it is possible.
Viewing 2 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply