May 8, 2013 at 9:37 am
We have our default background trace enabled. I am trying to find its SPID number. Does it have spid at all, and how to define it ?
May 8, 2013 at 9:40 am
when i run sp_who2, i see a few rows that might be the "right" server side spid(14,29 and in my case), with the command "TRACE QUEUE TASK"
why do you need the spid of a server side trace?
Lowell
May 8, 2013 at 9:57 am
Thanks Lowel, I found. It's #15 in my case. But sp_who2 is too large for me, it returns close to 1000 recs. So I actually ran
select * from sys.sysprocesses
where lastwaittype like '%trace%'
order by spid
Now, the reason why I need it. I am not happy with the info provided with default trace. It has almost nothing for performance, what it has is mostly connections info. I created my own trace, aimed particularly for performance. I run it from time to time in production. But before placing it to run it constantly in production, I want to compare their consumption metrics.
I can probably foresee your next advice - to use extended events. Yes, that's my next step, I need to learn it first.
May 8, 2013 at 10:07 am
we are really on the same page;
i use traces a LOt, especially becasue i'm very familiar with it, and it's easy to create a trace template with profiler, and make views to hit the results.
While i'm aware that extended events supposedly have a smaller impact, except for a few samples i've fiddled with, I'm not yet familiar enough with extended events to keep it at the top of the toolkit yet.
Lowell
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply