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 |
|
Sarat
Constraint Violating Yak Guru
265 Posts |
 Posted - 2003-06-11 : 16:29:55
|
| Hi,I have traced some amount of activity but I don't understand how to approach & what to interpret. For ex: I saw a select which had following info:CPU = 24969Reads = 497Duration = 25080Now how do I know whether these statistics are good or bad. Should I take the query, paste in Query Analyzer and study execution plan? and Ofcourse, where can I find in BOL which explains what each value means in the trace file coulmns?Thanks,Sarat.**To be intoxicated is to feel sophisticated, but not be able to say it.** |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-06-11 : 16:51:21
|
Well here's what I do:Trace into a tableRun this query on the table:SELECT TOP 100 Duration, TextDataFROM TraceTable --name of the trace tableWHERE TextData IS NOT NULL AND Duration > 5000 --took more than 5 seconds This query will show you the 100 worst performing queries.I then analyze these records by putting them into Query Analyzer to examine the execution plan as well as examining the T-SQL.I also will send the trace through the index tuning wizard as well.Tara |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2003-06-11 : 17:23:45
|
| Reads The number of logical reads performed (of 8K pages)Writes The number of logical writes performed (8k pages also)Duration How long the query ran in millisecondsCPU The amount of CPU time in milliseconds that was used. Profiler cannot show you the number of physical reads or writes, so that stat is not as useful as it could be. btw, your query is taking 25 seconds to run and is reading ~ 4MB of data. You should tune this one.-ecEdited by - eyechart on 06/11/2003 17:30:03 |
|
|
|
|
|
|
Traced data Analysis