December 29, 2007 at 8:48 am
I am a new user of SQL Profiler can anyone tell me how to set it up to track a specific Stored procedure when it fires.
I am trying to trouble shoot a problem I have with a stored procedure which provides data to a web report. I usually just manually step through the S.P. to figure out the issue but I have heard using SQL Profiler can be more efficient at finding errors and assisting with trouble shooting.
December 31, 2007 at 10:48 am
make the proc name a filter in text
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
January 8, 2008 at 10:48 am
thanks for your response -- I have been playing around with the tool and your right using the filters is the way to remove items from the trace. It seems to require some trial and error thought to get the specific results desired.
Thanks again for pointing me in the right direction
January 8, 2008 at 1:18 pm
I find not all filters quite work as you'd expect, and some give downright strange results - filtering by text seems to work usually and I use this if I want to profile against a particular table for instance.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply