How to stop a trace

Hi there,
I have a fairly simple question. How do you stop a trace in
SQL Profiler (2000 on XP)? When you click the stop button, the toolbar
changes and looks as though the trace has stopped but events are still being
added to the list, and when you try and exit the application, you get a
message about the trace still running. If you try to exit the application
hangs.
Waldy wrote:
> Hi there,
> I have a fairly simple question. How do you stop a
> trace in SQL Profiler (2000 on XP)? When you click the stop button,
> the toolbar changes and looks as though the trace has stopped but
> events are still being added to the list, and when you try and exit
> the application, you get a message about the trace still running. If
> you try to exit the application hangs.
You'll should wait until all events are processed. Maybe you have no
filter or a filter that is not very selective and thus get a large amount
of events. So it may take some time from pressing the button until all
events until then are processed (i.e. displayed).
Kind regards
robert
|||"Robert Klemme" <bob.news@.gmx.net> wrote in message
news:%232FhgwHtFHA.3864@.TK2MSFTNGP12.phx.gbl...
> You'll should wait until all events are processed. Maybe you have no
> filter or a filter that is not very selective and thus get a large amount
> of events.
I am only tracing one event on one database. How many hours do you suggest
I wait?
|||Waldy wrote:
> "Robert Klemme" <bob.news@.gmx.net> wrote in message
> news:%232FhgwHtFHA.3864@.TK2MSFTNGP12.phx.gbl...
> I am only tracing one event on one database. How many hours do you
> suggest I wait?
Dunno. Are you sure that the single event doesn't produce a lot of
entries? Otherwise I'm at a loss here, too. Sounds strange.
robert
|||Waldy wrote:
> Hi there,
> I have a fairly simple question. How do you stop a
> trace in SQL Profiler (2000 on XP)? When you click the stop button,
> the toolbar changes and looks as though the trace has stopped but
> events are still being added to the list, and when you try and exit
> the application, you get a message about the trace still running. If
> you try to exit the application hangs.
This can sometimes happen when using Profiler on a very busy server that
produces a lot of rowset information. Is your server under high load?
What event are you capturing and how much information is being returned
(you can see a rowcount in the status bar of the Profiler client).
In general, if you experience this problem, or are looking for a more
robust tracing method, you should use server-side tracing. A server-side
trace likely won't exhibit these problems. You can have Profiler script
the t-sql necessary to start the trace from the File - Script Trace menu
option. You need to roll your own code to stop the trace. You can open
the trace file directly in Profiler once the trace is stopped.
David Gugick
Quest Software
www.imceda.com
www.quest.com