February 24, 2015 at 7:59 am
Hi all
We have some Deadlock alerts set up in SQL Agent that email us when the performance counter for deadlocks goes above zero. I've used the following script to identify the event file which has deadlock information in there.
select CAST(target_data as xml) as TargetData
from sys.dm_xe_session_targets st
join sys.dm_xe_sessions s on s.address = st.event_session_address
where name = 'system_health'
Now that is fine, and we're looking into that (number of deadlocks appear to be 0.5) but out of interest ran a SQL Profiler session to capture the details as well and nothing is showing, I've received a few alerts and the trace file has information in there - but profiler shows absolutely nothing (all deadlock events are captured)
Any potential reasons why?
D
'Only he who wanders finds new paths'
February 24, 2015 at 12:53 pm
I'd only capture the deadlock graph event to minimize the impact of trace. Better still, why use trace? You're on 2012. Use extended events. It has a smaller footprint and less impact on the server than trace.
Not sure why you're not seeing it. It should work. Maybe you have a filter in place on the create script?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply