louis (lo************@gmail.com) writes:
I've got a new server with Pentium4 xeon processors. I've used sp_who2
for quite a while on my old server -- to look at CPU and IO usage. On
the new server, the CPU times are huge -- although actual performance
is quite good. I know sp_who2 is an undocumented proc. Has anyone
experienced this or is it just me?
sp_who2 gets the data from master..sysprocesses. It is difficult to say
what the changes are due to. But if the processes stays connected for a
long time, you will see high numbers.
One possible cause is that there are parallel query plans in use. The
optimizer appears to be fond of parallelism, but the parallel plans are
unfortunately always that effective.
--
Erland Sommarskog, SQL Server MVP,
es****@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp