|
Home > Archive > MS SQL Server > January 2006 > profiler
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Andre Gibson 2006-01-18, 8:23 pm |
| 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?
| |
| P. Ward 2006-01-18, 8:23 pm |
| 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(def
ault)
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?
| |
| Andre Gibson 2006-01-18, 8:23 pm |
| thanks so much Peter,
I will try that
"P. Ward" wrote:
[color=darkred]
> 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(def
ault)
>
> 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:
>
|
|
|
|
|