SQL Server Performance Forum – Threads Archive

Server trace in QA

Hello If I execute a stored procedure with profiler running showing completed statements, i can pretty much add up the ‘duration’ column (which seems to be in milliseconds) and get a time that is equivalent to the time the sp took to complete. However, if I enable ‘Show server trace’ in Query Analyzer and run the same SP, the ‘duration’ column does not add up. I just ran one SP that took 43 seconds to complete, but the ‘duration’ column adds up to only just below 3 seconds (assuming it IS milliseconds…) So, questions:
Is the duration in profiler and server trace supposed to be milliseconds?
Why is the server trace giving me completely different figures? thanks /linus —
http://anticAPSLOCK.com

http://www.databasejournal.com/features/mssql/article.php/2239461 for information on running server traces. HTH Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Thanks for the reply The article confirmed that ‘duration’ is in milliseconds, but it does not mention server trace in QA at all. It would be very convenient to measure a the execution of a SP if you could just enable ‘show server trace’ in QA and execute it, rather than setting up a profiler session with filters for pid, etc… /linus —
http://anticAPSLOCK.com

QA & PROFILER are two different processes and joining them may stress the server and we can expect such facility in future release of SQL server. In this case running server side trace would help to reduce stress on Server while using GUI tool. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Not sure what you mean: You can already chose ‘show server trace’ in QA and it will show what happens, it’s just that it seems to have the duration wrong… /l —
http://anticAPSLOCK.com

Run the client trace also. See how long the response takes to reach the client. Add that number to the duration received from the trace file. See if that matches the server trace in QA. MeanOldDBA
[email protected] When life gives you a lemon, fire the DBA.

]]>