I suggest you ...

Show Stored Procedure Argument values in Long Running Query alerts

Showing me the CREATE PROCEDURE XXX_sp would be far more helpful if I could see what parameters had been passed into the procedure.

The run times of some of our procedures vary significantly depending on the client or account they are being run for. Knowing what values were passed in to the SP is essential information in troubleshooting the problem.

16 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Kyle LeesmanKyle Leesman shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Daniel RothigAdminDaniel Rothig (Software Engineer, Red Gate Software) commented  ·   ·  Flag as inappropriate

        Thanks for getting back to me, Kyle! AppDynamics seems to hook into client code or otherwise intercept requests from managed code, which is quite a bit more invasive than what we do. For us, there might be a way of doing this, but it's quite involved and risks putting load on the monitored server (and SQL Monitor aims to be lightweight!) I'm going to remove the "Under Review" status for now, to see if the suggestion proves popular enough to warrant the required engineering effort.

        Thanks again for your feedback!

      • Kyle LeesmanKyle Leesman commented  ·   ·  Flag as inappropriate

        I did a trial of I think AppDynamics monitoring a while back and it is able to report the exact SP and parameters run. Maybe they're able to because they install an agent on the server.

      Feedback and Knowledge Base