Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
 Posted - 2007-05-02 : 00:37:03
|
Hi,I'm trying to figure out why my sqlserver is flatlined on the CPU. I'm doing a trace and can't help but notice this, with crazy high reads. I'm not sure what this is? It doesnt look good to me, altho maybe its nothing. Any info is much appreciated.Thanks again!mike123Event Class/ TextData/ApplicationName/ LoginName/ CPU/ Reads/ Writes/ DurationAudit Logout .Net SqlClient Data Provider loginName 376 4129784 3146 156 |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2007-05-02 : 11:10:48
|
| It would be close to nothing. The number you are seeing is an aggregate of all the reads the connection has made during its lifetime. Same for CPU. |
 |
|
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
Posted - 2007-05-02 : 19:51:50
|
| thanks :) |
|
|
|
DBSEC
Starting Member
2 Posts |
Posted - 2007-06-07 : 18:05:23
|
quote:
Originally posted by mike123Event Class/ TextData/ApplicationName/ LoginName/ CPU/ Reads/ Writes/ DurationAudit Logout .Net SqlClient Data Provider loginName 376 4129784 3146 156
Unless the duration was somehow truncated I would look into this further. The problem is that the duration is 156 milliseconds (assuming SQL Server 2000 - if this is a 2005 it's in microseconds). This means the connection generated 4 million reads in 156 milliseconds... if this is an OLTP server I would be concerned. |
|
|
|
|
|
|
Audit Logout, High Reads