March 13, 2015 at 2:38 pm
Hello experts,
In order to troubleshoot some deadlocking that I am seeing on SQL Server, I am trying to capture the Deadlock XML by enabling the Events Extraction Settings option 'Save Deadlock XML events separately' and specifying a Deadlock XML results file.
Meanwhile, I am also tracing the Deadlock graph, Lock:Deadlock, and Lock:Deadlock Chain events. Yet the xdl file remains empty even though I am getting hits on the events themselves in the SQL Profiler trace.
Also, I have the following trace flag settings enabled.
TraceFlagStatusGlobalSession
1204110
1222110
Does anyone know why the xdl file remains empty even though (I think) it should contain some XML for deadlocks that are actually happening?
Thanks in advance for any help. Let me know if any other info would help diagnose this.
- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
March 13, 2015 at 3:18 pm
Is it simply blocking or is it dead-locking?
😎
A comic situation would be two threads trying to write to the deadlock file at the same time...:-D
March 13, 2015 at 3:22 pm
Eirikur Eiriksson (3/13/2015)
Is it simply blocking or is it dead-locking?😎
A comic situation would be two threads trying to write to the deadlock file at the same time...:-D
Hello, thanks for your response.
Yes, it is definitely deadlocking. I use Red Gate SQL Monitor as well, and it reports the deadlock info. I just want to get the deadlock graph as well, but for some reason the xdl file remains at 0 K.
Thanks again for any help!
- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
March 15, 2015 at 2:31 pm
webrunner (3/13/2015)
Eirikur Eiriksson (3/13/2015)
Is it simply blocking or is it dead-locking?😎
A comic situation would be two threads trying to write to the deadlock file at the same time...:-D
Hello, thanks for your response.
Yes, it is definitely deadlocking. I use Red Gate SQL Monitor as well, and it reports the deadlock info. I just want to get the deadlock graph as well, but for some reason the xdl file remains at 0 K.
Thanks again for any help!
- webrunner
Quick question, have you checked permissions etc.? Any other files empty or successfully written?
😎
March 16, 2015 at 7:16 am
Eirikur Eiriksson (3/15/2015)
webrunner (3/13/2015)
Eirikur Eiriksson (3/13/2015)
Is it simply blocking or is it dead-locking?😎
A comic situation would be two threads trying to write to the deadlock file at the same time...:-D
Hello, thanks for your response.
Yes, it is definitely deadlocking. I use Red Gate SQL Monitor as well, and it reports the deadlock info. I just want to get the deadlock graph as well, but for some reason the xdl file remains at 0 K.
Thanks again for any help!
- webrunner
Quick question, have you checked permissions etc.? Any other files empty or successfully written?
😎
Thanks for your response!
I do see that the .trc files are successfully written to. Is that what you have in mind?
Also, I am using SQL Profiler, so the files are writing to a folder I created on the C drive of my local computer. (This is only a short trace - I have read about all of the downsides of using SQL Profiler.) I normally use a server-side trace but am not sure the xdl file can be collected via server-side trace. If there is a way to do that, should I try that method instead?
Thanks again for any help,
webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply