December 3, 2008 at 9:23 am
I incorrectly titled this topic. Really it should be: Low Statistics Logical Reads and High Profiler Reads.
I have a proc that when traced in Profiler (all default settings) reports CPU 78 Reads of 42422.
When I run this proc with STATISTICS TIME and IO on it reports this:
SQL Server Execution Times:
CPU time = 0 ms, elapsed time = 0 ms.
SQL Server Execution Times:
CPU time = 0 ms, elapsed time = 0 ms.
SQL Server parse and compile time:
CPU time = 0 ms, elapsed time = 0 ms.
Table 'tLE. Scan count 26, logical reads 52, physical reads 0, read-ahead reads 0.
Table 'tDN'. Scan count 28, logical reads 56, physical reads 0, read-ahead reads 0.
Table 'tCA'. Scan count 2, logical reads 362, physical reads 0, read-ahead reads 0.
SQL Server Execution Times:
CPU time = 31 ms, elapsed time = 38 ms.
(1 row(s) affected)
SQL Server Execution Times:
CPU time = 31 ms, elapsed time = 38 ms.
To me it seems like the Reads in Profiler are way higher than they should be. Any input on this? TIA!
December 3, 2008 at 9:33 am
I've had the same issue few times a while ago. I don't remember the exact numbers but it was similar to your case (the QA shows few hundreds logical reads and the profiler shows few hundred thousands of logical reads). I couldn't find an explanation for that, but I do remember that the profiler was correct and not the QA.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 3, 2008 at 9:37 am
Thanks Adi for the reply....
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply