May 11, 2003 at 8:43 pm
I'm using SQL Server 2000 Enterprise
SQL SP 2
One of our dev guys has a group of sps that run late at night. Now he asked to just find out when a particular sp starts and finishes
now when i setup the trace to filter so only the sp we want to monitor is traced. it doesnt work, i still get all the other crap. but if i filter on user name it works .
Is this a bug with Profiler ?
how do i get the trace to just log the sp i want ?
Thanks.
Steve
May 12, 2003 at 1:26 am
I have noticed that SQL Profiler filters seem to be case sensitive. Check to see if your filter exactly matches the EXEC being submitted by your dev guy.
May 12, 2003 at 3:00 am
Also, some Events do not seem to work against the filters so you will get anything that happens.
May 12, 2003 at 4:47 pm
Cheers guys
I triple checked the case ...
....Is this a limit or a bug ?
is there a workaround ?, the process I want to monitor takes place at 11pm and goes on for a few hours there would be a lot of output generated from a trace that captures everything .
May 13, 2003 at 5:21 am
I think in what I stated it is a limit of the filter interaction with the event. Capture only what you need in regards to events. For example things like SP:CacheMiss are picked up in all DBs even though I set a DB filter. Just make sure you go after only what you need.
May 15, 2003 at 6:52 pm
I too have noticed issues with the Profiler since SP2. In my case, it is filtering on database name. I have had to resort to filtering on database id instead.
I did try the database name in the correct case, all lower case, and all upper case...all to the same effect. Switching to database id worked correctly.
David R Buckingham, MCDBA,MCSA,MCP
May 15, 2003 at 9:16 pm
In 6.5 tracing was easier... well at least you could import the file into Excel but not any more unless anyone knows of a way ??.
I suppose you could capture to a table and then import into excel.
May 19, 2003 at 9:44 pm
stevekeily,
You can use fn_trace_getinfo to return just the trace records you want by specifying an appropriate WHERE clause. You could use that in conjunction with bcp to create a CSV data file for import into Excel.
David R Buckingham, MCDBA,MCSA,MCP
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply