I need to trace the execution of a SP that has been identified as "problematic". If I do not want to modify the SP with tracing code, can I trace it with profiler an see where exactly the SP spends more time. This SP in turns call about 30 other SP....
You can imagine that it's a pain to pinpoint the source of the problem.
Currently, in profiler using the "tuning" template, I can see that the SP takes about 4 hours to complete.