Pablo Sanchez (ho******@blueoakdb.com) writes:
Erland Sommarskog <so****@algonet.se> wrote in
news:Xn**********************@127.0.0.1:
What's wrong with sysprocesses?
In the 'olden' days (Sybase 4.x/10.x) the values weren't valid. Are
they considered valid nowadays?
Sorry for the delay, but I tried to consult with my MVP colleagues and
the Microsoft people, if I would get any response.
I can't vouch for that all these values are extremely valid, but then
again, I don't think you will find anything better.
The ones on memory and CPU may be OK. Logical reads is a problem, because
with the new query strategies in SQL 7 and SQL 2000, the value reflected
by logical reads in SET STATISTICS IO may not always be accurate. And if
it's not accurate there, it is not likely to be accurate in sysprocesses
either. Still the value you see is probably good indication.
Of course, you can also use the performance monitor, but I don't think
you will find per-spid values there.
--
Erland Sommarskog, SQL Server MVP,
so****@algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp