I'm looking for some insight/ideas/shots in the dark on this one . My client has a trace running and wants to filter out Error=208, Severity=16, State<=1. The way I've found that tracing scripts work with sp_trace_setfilter is that you can't group those requirements like a where clause. This script should show what I'm looking for.[code="sql"]-- Create a Queuedeclare @rc intdeclare @TraceID intdeclare @maxfilesize bigintset @maxfilesize = 5 exec @rc = sp_trace_create @TraceID output, 0, N'InsertFileNameHere', @maxfilesize, NULL if (@rc != 0) goto error-- Set the eventsdeclare @on bitset @on = 1exec sp_trace_setevent @TraceID, 21, 10, @onexec sp_trace_setevent @TraceID, 21, 20, @onexec sp_trace_setevent @TraceID, 21, 30, @onexec sp_trace_setevent @TraceID, 21, 31, @on-- Set the Filtersdeclare @intfilter intdeclare @bigintfilter bigintexec sp_trace_setfilter @TraceID, 10, 0, 7, N'SQL Server Profiler - 618fcdf0-b48a-4d89-9ec1-4288a8520be5'set @intfilter = 16exec sp_trace_setfilter @TraceID, 20, 0, 1, @intfilterset @intfilter = 1exec sp_trace_setfilter @TraceID, 30, 0, 5, @intfilterset @intfilter = 208exec sp_trace_setfilter @TraceID, 31, 0, 1, @intfilter-- Set the trace status to startexec sp_trace_setstatus @TraceID, 1-- display trace id for future referencesselect TraceID=@TraceIDgoto finisherror: select ErrorCode=@rcfinish: go[/code]I'm looking for a way to take all 3 criteria into consideration instead of individually.[code="sql"]Where (set @intfilter = 16exec sp_trace_setfilter @TraceID, 20, 0, 1, @intfilterANDset @intfilter = 1exec sp_trace_setfilter @TraceID, 30, 0, 5, @intfilterANDset @intfilter = 208exec sp_trace_setfilter @TraceID, 31, 0, 1, @intfilter)[/code]
↧