When I’m faced with app. debugging, especially procedures that take awhile to run, or require a series of steps in the application to fire off, I often use SQL Profiler to capture the SQL call. Then I’ll re-run the call directly in SQL Management Studio. But SQL Profiler can bring back a lot of noise, making it tough to grab only what I need.
I finally created a custom trace template and set it to be my default. It will only show me calls made from my local workstation to the development database. (we have a shared development database*)
This article will help you set up a personalised trace. For expample you can filter by Application Name or Host Name to reduce the noise in your trace.