|
Home > Archive > MS SQL Server > October 2006 > SQL 2005 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]
|
|
| Tim Kelley 2006-10-25, 6:00 am |
| I had stared a trace on one of my sql servers (2005) but I cannot stop it.
I must have closed the profiler program before I stopped the trace. Is
there a way to stop it?
Thanks.
| |
| Hilary Cotter 2006-10-25, 6:00 am |
| It should have stopped when you stopped profiler.
You should be able to see it when you issue a sp_who2, it will show up with
an Program name of
SQL Server Profiler - 8c1959da-f85d-463d-8a6b-eb8292dd3c69 or something like
that.
Use the kill command to kill it..
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tim Kelley" <tkelley@company.com> wrote in message
news:uW6IMds9GHA.4196@TK2MSFTNGP03.phx.gbl...
>I had stared a trace on one of my sql servers (2005) but I cannot stop it.
>I must have closed the profiler program before I stopped the trace. Is
>there a way to stop it?
>
> Thanks.
>
| |
| Kalen Delaney 2006-10-25, 6:00 am |
| Does it show up with select * from sys.traces?
If so, you can use sp_trace_setstatus to stop it.
Please see Books Online for details.
--
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Tim Kelley" <tkelley@company.com> wrote in message
news:uW6IMds9GHA.4196@TK2MSFTNGP03.phx.gbl...
>I had stared a trace on one of my sql servers (2005) but I cannot stop it.
>I must have closed the profiler program before I stopped the trace. Is
>there a way to stop it?
>
> Thanks.
>
|
|
|
|
|