November 23, 2008 at 6:05 pm
Hello,
I've noticed that over my holidays some start cookie has created a .trc file which has been running for a couple of days now and i would like to know how can i find out from what pc it was created on so i can stop it.
Cheers 🙂
Remember
Without Change something sleeps inside of us that seldom awakens, the sleeper must awaken!!
November 23, 2008 at 9:45 pm
Do you mean your server has a trace file running?
This doesn't mean profiler is running. You can kill the trace.
Or examine connections to your instance.
November 23, 2008 at 9:49 pm
Yeah, a profiler trace is running on the server and i wanna from which machine its running from.
Remember
Without Change something sleeps inside of us that seldom awakens, the sleeper must awaken!!
November 23, 2008 at 9:59 pm
May be dafault trace running :
to stop :
sp_configure 'default trace enabled',0
go
reconfigure
go
Find running trace :
select * from fn_trace_getinfo(0)
November 23, 2008 at 10:04 pm
Thanks Paresh,
You where bang on , default profile trace had been switched on.
Cheers 🙂
Remember
Without Change something sleeps inside of us that seldom awakens, the sleeper must awaken!!
November 24, 2008 at 10:57 am
Mr J (11/23/2008)
Yeah, a profiler trace is running on the server and i wanna from which machine its running from.
In SQL Server Management Studio, open the Management folder, and select activity monitor. One of these should be the profiler (you'll see the words profiler and/or Trace). Look at the hostname column and that should narrow it down.
Gaby________________________________________________________________"In theory, theory and practice are the same. In practice, they are not." - Albert Einstein
November 25, 2008 at 5:28 am
Default trace is never switched on, it is on by default.
You might want to consider carefully whether you want to go ahead and switch it off for no particular reason: it costs very little in overhead to run and it captures a good deal of information that can help you troubleshoot your instance of SQL Server.
Just a thought.
November 25, 2008 at 6:39 am
Also the default trace is used as the source for many of the reports available in SSMS. So if you disable it you will lose those reports as well.
There is no real reason to stop it. I have answered many questions for SQL Server 7, 2000 that would have had an an easy answer if those versions had the default trace running.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
November 25, 2008 at 7:17 am
Ease way to find trace is following :
select * from fn_trace_getinfo(0) where value = 5 --
if default trace is running then value is 1 , then we can capture other trace id
We can stop it from following command:
exec sp_trace_setstatus 'traceid -- which got from upper query' ,0
November 25, 2008 at 7:21 am
Just to note in SQL Server 2005 and later you get better information by querying sys.traces instead of fn_tracegetinfo and is actually the recommended method.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
November 25, 2008 at 3:17 pm
Cheers everyone for the wealth of knowlegde 🙂
Remember
Without Change something sleeps inside of us that seldom awakens, the sleeper must awaken!!
November 25, 2008 at 3:29 pm
to make the trace easier to read\sort dump the output to a sql table
SELECT * INTO tablename
FROM ::fn_trace_gettable('d:\path to trace\tracename.trc', default)
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply