March 5, 2008 at 9:10 am
Hi
I've got SQL Profiler running on one of our machines, but it shows 0 for CPU, Reads and Writes - for every single event, including ones that are clearly returning data. Obviously this can't be right, so I was wondering if anyone else had ever had a similar problem?
We're running SQL 2000 Standard SP3 on Windows Server 2003 SP1.
Thanks,
Duncan
March 17, 2008 at 4:53 pm
It could have sense sometimes... Using the Profiler that comes with the Management Console of SQL Server 2005 against a SQL Server 2000 server could give these results 😉
Virgil Rucsandescu
March 18, 2008 at 8:04 am
Hi
I should probably have said I'm using the 2000 version of SQL Profiler, and running it on the same server that I'm looking at.
On closer inspection I do in fact get the occasional positive value in the cpu column (for "Audit Logout" events) and the write column does appear normal after all (sorry). However I have nothing appearing above 0 in the reads column as yet. Is there any logical reason why that might be the case?
Duncan
March 18, 2008 at 10:18 am
What if you add counter filters, say, CPU > 0?
March 20, 2008 at 4:41 am
Hi
Thanks for responding. I've done some more digging and the CPU shows positive values for a few SP:StmtCompleted events (reads show zero for those, even though they contain select statements)
The filter for reads > 0 throws up plenty of rows with NULL values for reads (still nothing greater than zero though), which are all SP:Completed events. I also have it looking at RPC:Completed, SP:StmtCompleted, SQL:BatchCompleted and SQL:StmtCompleted, but these don't show up at all with the read filter. Are there any others I should be looking at that should definitly show reads if all is well?
Duncan
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply