When you see time allocated to a proxy procedure in the stored procedure profiler, and you expand it to see the source code, all it can show is the CREATE PROCEDURE definition... utterly useless for the purposes of performance optimization.

If the database has hundreds of proxy procedures, and a few real procedures you are interested in, seeing those hundreds of proxy procedures cluttering up the list is quite an annoyance. It is quite sufficient to see the time spent in those procedures shown against the CALL statements in the real procedures.

asked 01 Apr '11, 15:42

Breck%20Carter's gravatar image

Breck Carter
26.2k430599862
accept rate: 20%

Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×107

question asked: 01 Apr '11, 15:42

question was seen: 656 times

last updated: 01 Apr '11, 15:42