Find out which store procedures were fired

Question

Post reply

Find out which store procedures were fired

adonetok

SSCrazy Eights

Points: 8395
More actions
April 16, 2014 at 6:55 am

#287684

Our company purchased a app.
Is there any way to find out which store procedures were fired once a button was clicked?

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

tim_harkin SSCrazy Points: 2399 More actions · Answer 1

SQL Profiler. Possible Extended Events as well, but I am not sure about that.

Koen Verbeeck SSC Guru Points: 259115 More actions · Answer 2

tim_harkin (4/16/2014)
SQL Profiler. Possible Extended Events as well, but I am not sure about that.

Since profiler is deprecated and to be fully replaced with Extended Events, you can be fairly certain it is possible with Extended Events as well.

XE also has the benefit of having a lower performance impact on the production system than profiler.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Jeff Moden SSC Guru Points: 1004392 More actions · Answer 3

Koen Verbeeck (4/16/2014)
Since profiler is deprecated and to be fully replaced with Extended Events, you can be fairly certain it is possible with Extended Events as well.

We're still stuck on 2005 at work (hopefully migrating to 2014 in late summer) so I've not had the joy of playing with Extended Events in a production environment but it always scares the hell out of me when old tried'n'true methods are replaced because they seem to always leave something out. Things like the {f4} key in old Query Analyzer didn't make it into SSMS and it was some really helpful and easy to use functionality when you really needed it.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)