October 1, 2009 at 7:20 am
Hi,
How can i find out which one of the procedure need to be optimize in the server profiler?
thanks in advance...
regards,
Ananth
October 1, 2009 at 7:33 am
the interesting columns are:
CPU, Reads, Writes and Duration.
Regards
Alex
October 1, 2009 at 7:35 am
Duration column within profiler indicates how long the process took in milliseconds.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
October 1, 2009 at 9:55 am
What you have to do is import the data from Profiler into a table (preferably not a production server). Then you clean the ouput, basically removing parameters from the Text data field. From there you can begin aggregating the data. Group the data to get execution count and average duration. Usually, working off these two values will give you the worst performing procedures.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 1, 2009 at 12:09 pm
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 1, 2009 at 12:11 pm
Melton (10/1/2009)
Duration column within profiler indicates how long the process took in milliseconds.
Depends.
SQL 2005 and above actually measure duration in microseconds, not milliseconds. There's an option in the profiler GUI that determines whether duration is displayed in milliseconds or microseconds. If the trace file is queried or loaded into a SQL table, then the stored duration is in microseconds.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply