Re: SQL Profiler Filters

From: Derek Ruesch (DerekRuesch_at_discussions.microsoft.com)
Date: 01/19/05 

Date: Wed, 19 Jan 2005 09:03:06 -0800

Nevermind this problem. I figured it out on my own. All you need to do is
type in, for example UPDATE%, (without the single quotes sign). This example
will only retrieve "UPDATE" SQL statements.

I do have another question though. Once you have created a trace and then
stopped it. How do you restart it so that you can continue tracing events. I
closed SQL Profiler before I went home last night (this stopped the trace)
and then I wanted to start the trace again this morning. However it only lets
you "replay" the trace file. I don't want to replay the trace file, I want it
to continue tracing events. Is there any way to make it resume tracing events
after you have stopped it or make it trace events even after profiler has
been closed?

Thanks for your help.

Derek Ruesch

"Kalen Delaney" wrote:

> Hi Derek
>
> I am had some problems with multiple filters working correctly together,
> especially when you include negatives. There may be a bug in the trace
> engine itself or it may be a bug in how Profiler translates your filters to
> an underlying trace.
>
> What version are you using? (That info should always be included when asking
> for help.)
>
> I presume from your subject line you are using Profiler, and not a server
> side trace. Can you see what trace command your filters are being converted
> to?
> If you are using SQL 2000, you can. Use the option on the profiler menu to
> script the trace, and save the script to a file. Then show us the lines from
> the script that include sp_trace_setfilter.
>
> --
> HTH
> ----------------
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
>
> "Derek Ruesch" <DerekRuesch@discussions.microsoft.com> wrote in message
> news:34906C19-26EE-4926-B80F-B6B4E0C45879@microsoft.com...
> >I have a SQL Profiler trace that has the following filters applied:
> >
> > Application Name Not Like SQL Profiler
> > TextData Not Like SELECT
> >
> > I want this trace to not include SQL Profiler events and SQL "Select"
> > statements.
> >
> > The trace does not show SQL Profiler events but it does still show
> > "Select"
> > SQL statements. Why is it still showing SQL Select statements?
> >
> > Thanks for the help.
> >
> > Derek Ruesch
>
>
>

Relevant Pages

  • Re: SQL 7 Traces
    ... Profiler 2K can generate the xp calls for a defined trace in 7 format. ... Tibor Karaszi, SQL Server MVP ...
    (microsoft.public.sqlserver.programming)
  • Re: Wartungsfreier SQL-Server!?
    ... wenn man sonst keine Anhaltspunkte hat. ... Wie kann ich den "SQL Profiler Trace" mir anzeigen lassen? ...
    (microsoft.public.de.sqlserver)
  • Re: Monitor SQL Statements
    ... First off you should never use Profiler for traces on busy systems. ... Then run the trace and immediately hit ... Andrew J. Kelly SQL MVP ...
    (microsoft.public.sqlserver.security)
  • Re: Simple timeout problem
    ... Brian, I haven't found anything specific on this error. ... We'd want to limit the trace to just the BizTalkRuleEngineDB. ... To run a trace go to SQL Profiler (under the SQL Server entry in the start ... | are reporting a timeout condition trying to connect to the SQL database. ...
    (microsoft.public.biztalk.general)
  • Re: Profiler Bug viewing trace flat file?
    ... Kalen Delaney, SQL Server MVP ... Run this code to create a trace capture of the RPC:Complete event: ... declare @error INT ... Now open the trace file in Profiler and you will see that the Textdata ...
    (microsoft.public.sqlserver.tools)
Quantcast