Comments on: The Ultimate Strategy of Tuning Store Procedure Performance http://www.siusic.com/wphchen/the-ultimate-strategy-of-tuning-store-procedure-performance-46.html Random thoughts and news by Andrew Chen and friends Fri, 30 Jul 2010 21:51:47 +0000 http://wordpress.org/?v=2.5 By: Andrew Chen http://www.siusic.com/wphchen/the-ultimate-strategy-of-tuning-store-procedure-performance-46.html#comment-31 Andrew Chen Thu, 25 Jan 2007 18:27:59 +0000 http://www.siusic.com/wphchen/the-ultimate-strategy-of-tuning-store-procedure-performance-46.html#comment-31 I finally found a chance to test out the way to use profiler trace that you suggest. I actually try that way long time ago and I even forgot about why I didn’t may use of it. But I still come to the same conclusion. I don’t think that kind of tracing is helpful for complex store procedure tuning. In fact in that kind of trace profiler displays every single statement executed within the store procedure. So if your store procedure has cursor operations, loops and nested call to other store procedures and functions then the trace result could be many thousands lines of text. It could be a lot more in fact. How are you going to make use of it? I am not talking about simple store procedures. The result is that you could not get a big picture of how the store procedure is written and which piece of code should be rewritten to improve performance. I still believe in my ultimate strategy. It have help me solved numerous performance tuning problems. I finally found a chance to test out the way to use profiler trace that you suggest. I actually try that way long time ago and I even forgot about why I didn’t may use of it.

But I still come to the same conclusion. I don’t think that kind of tracing is helpful for complex store procedure tuning. In fact in that kind of trace profiler displays every single statement executed within the store procedure. So if your store procedure has cursor operations, loops and nested call to other store procedures and functions then the trace result could be many thousands lines of text. It could be a lot more in fact. How are you going to make use of it?

I am not talking about simple store procedures. The result is that you could not get a big picture of how the store procedure is written and which piece of code should be rewritten to improve performance.

I still believe in my ultimate strategy. It have help me solved numerous performance tuning problems.

]]> By: Andrew Chen http://www.siusic.com/wphchen/the-ultimate-strategy-of-tuning-store-procedure-performance-46.html#comment-24 Andrew Chen Sat, 06 Jan 2007 21:48:18 +0000 http://www.siusic.com/wphchen/the-ultimate-strategy-of-tuning-store-procedure-performance-46.html#comment-24 I don't remember for what reason I have this thought or maybe a misconception that the duration given on the statements tracing didn't really reflects the real time that a client experience. Your post certainly opens my eye. Thanks for the response. I don’t remember for what reason I have this thought or maybe a misconception that the duration given on the statements tracing didn’t really reflects the real time that a client experience. Your post certainly opens my eye. Thanks for the response.

]]> By: Scott Whigham http://www.siusic.com/wphchen/the-ultimate-strategy-of-tuning-store-procedure-performance-46.html#comment-23 Scott Whigham Sat, 06 Jan 2007 15:54:44 +0000 http://www.siusic.com/wphchen/the-ultimate-strategy-of-tuning-store-procedure-performance-46.html#comment-23 Interesting approach but it sure seems you're going about this the "long way." If you want to eliminate this step of copy/pasting the source code and having to find all the myraid calls to the proc, I would suggest that you set Profiler to trace the SP:Statement(s) events instead of the SP:Completed or RPC:Completed events. Once you do that, save the trace as a table, and then query the "Duration" column (or the StartTime/EndTime). Problem solved without any code writing! Interesting approach but it sure seems you’re going about this the “long way.” If you want to eliminate this step of copy/pasting the source code and having to find all the myraid calls to the proc, I would suggest that you set Profiler to trace the SP:Statement(s) events instead of the SP:Completed or RPC:Completed events. Once you do that, save the trace as a table, and then query the “Duration” column (or the StartTime/EndTime). Problem solved without any code writing!

]]>