profiler

I stsrted a trace on one of my bds and it is creating mulitple 5 mb files. I
thought it would stop once I closed the profiler. WRONG!!!
How can I stop this?
You can use the following TSQL statement to identify the TraceID of any
Traces that are currently running:
SELECT DISTINCT traceid FROM :: fn_trace_getinfo(default)
You can then stop any running traces by setting the status of the TraceID to
stopped (0).
ie.
EXEC sp_trace_setstatus @.traceid = 1,
@.status = 0
HTH
- Peter Ward
WARDY IT Solutions
"Andre Gibson" wrote:

> I stsrted a trace on one of my bds and it is creating mulitple 5 mb files. I
> thought it would stop once I closed the profiler. WRONG!!!
> How can I stop this?
|||thanks so much Peter,
I will try that
"P. Ward" wrote:
[vbcol=seagreen]
> You can use the following TSQL statement to identify the TraceID of any
> Traces that are currently running:
> SELECT DISTINCT traceid FROM :: fn_trace_getinfo(default)
> You can then stop any running traces by setting the status of the TraceID to
> stopped (0).
> ie.
> EXEC sp_trace_setstatus @.traceid = 1,
> @.status = 0
> HTH
>
> - Peter Ward
> WARDY IT Solutions
>
> "Andre Gibson" wrote:

profiler

I stsrted a trace on one of my bds and it is creating mulitple 5 mb files. I
thought it would stop once I closed the profiler. WRONG!!!
How can I stop this?You can use the following TSQL statement to identify the TraceID of any
Traces that are currently running:
SELECT DISTINCT traceid FROM :: fn_trace_getinfo(default)
You can then stop any running traces by setting the status of the TraceID to
stopped (0).
ie.
EXEC sp_trace_setstatus @.traceid = 1,
@.status = 0
HTH
- Peter Ward
WARDY IT Solutions
"Andre Gibson" wrote:
> I stsrted a trace on one of my bds and it is creating mulitple 5 mb files. I
> thought it would stop once I closed the profiler. WRONG!!!
> How can I stop this?|||thanks so much Peter,
I will try that
"P. Ward" wrote:
> You can use the following TSQL statement to identify the TraceID of any
> Traces that are currently running:
> SELECT DISTINCT traceid FROM :: fn_trace_getinfo(default)
> You can then stop any running traces by setting the status of the TraceID to
> stopped (0).
> ie.
> EXEC sp_trace_setstatus @.traceid = 1,
> @.status = 0
> HTH
>
> - Peter Ward
> WARDY IT Solutions
>
> "Andre Gibson" wrote:
> > I stsrted a trace on one of my bds and it is creating mulitple 5 mb files. I
> > thought it would stop once I closed the profiler. WRONG!!!
> >
> > How can I stop this?

profiler

I stsrted a trace on one of my bds and it is creating mulitple 5 mb files. I
thought it would stop once I closed the profiler. WRONG!!!
How can I stop this?You can use the following TSQL statement to identify the TraceID of any
Traces that are currently running:
SELECT DISTINCT traceid FROM :: fn_trace_getinfo(default)
You can then stop any running traces by setting the status of the TraceID to
stopped (0).
ie.
EXEC sp_trace_setstatus @.traceid = 1,
@.status = 0
HTH
- Peter Ward
WARDY IT Solutions
"Andre Gibson" wrote:

> I stsrted a trace on one of my bds and it is creating mulitple 5 mb files.
I
> thought it would stop once I closed the profiler. WRONG!!!
> How can I stop this?|||thanks so much Peter,
I will try that
"P. Ward" wrote:
[vbcol=seagreen]
> You can use the following TSQL statement to identify the TraceID of any
> Traces that are currently running:
> SELECT DISTINCT traceid FROM :: fn_trace_getinfo(default)
> You can then stop any running traces by setting the status of the TraceID
to
> stopped (0).
> ie.
> EXEC sp_trace_setstatus @.traceid = 1,
> @.status = 0
> HTH
>
> - Peter Ward
> WARDY IT Solutions
>
> "Andre Gibson" wrote:
>

profiler

I stsrted a trace on one of my db's and it is creating mulitple 5 mb files.
I
thought it would stop once I closed the profiler. WRONG!!!
How can I stop this?Is there some service I can restart that will end this without me having to
restart the server.
"Andre Gibson" wrote:

> I stsrted a trace on one of my db's and it is creating mulitple 5 mb files
. I
> thought it would stop once I closed the profiler. WRONG!!!
> How can I stop this?
>|||Did you select the "server side trace" checkbox? If so, you have a server si
de trace running, which
is disconnected from the Profiler GUI. It will stop if you restart the SQL S
erver. Or you can stop
it explicitly. First find out the ID of the trace using fn_trace_getinfo. Th
en stop and close the
trace using sp_trace_setstatus. You need to first stop (0) and then close (2
).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Andre Gibson" <AndreGibson@.discussions.microsoft.com> wrote in message
news:19BEFA5A-5395-4611-BE1C-B9D81315A781@.microsoft.com...
>I stsrted a trace on one of my db's and it is creating mulitple 5 mb files.
I
> thought it would stop once I closed the profiler. WRONG!!!
> How can I stop this?
>|||thanks Tibor
"Tibor Karaszi" wrote:

> Did you select the "server side trace" checkbox? If so, you have a server
side trace running, which
> is disconnected from the Profiler GUI. It will stop if you restart the SQL
Server. Or you can stop
> it explicitly. First find out the ID of the trace using fn_trace_getinfo.
Then stop and close the
> trace using sp_trace_setstatus. You need to first stop (0) and then close
(2).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Andre Gibson" <AndreGibson@.discussions.microsoft.com> wrote in message
> news:19BEFA5A-5395-4611-BE1C-B9D81315A781@.microsoft.com...
>