Red Gate forums :: View topic - SQL Response reports deadlocks where SQl server does not rep
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Response 1
SQL Response 1 forum

SQL Response reports deadlocks where SQl server does not rep

Search in SQL Response 1 forum
Post new topic   Reply to topic
Jump to:  
Author Message
JeroenvH



Joined: 24 Jun 2010
Posts: 3

PostPosted: Thu Jun 24, 2010 1:12 pm    Post subject: SQL Response reports deadlocks where SQl server does not rep Reply with quote

Hello,

I'm evaluating SQL Response right now, and I encounter the following:

SQL Reponse is reporting strange deadlocks: The victim SPID for example is 0.

The running Porofiler trace (with deadlock graph on) does NOT report a deadlock; also does the perfmon counter deadlock/sec not increase.

Why does sql-response report a deadlock where SQL-Server does not ?

The detailed info from sql-reponse:

Deadlock encountered .... Printing deadlock information
Wait-for graph

Node:1
Port: 0x00000001D467C960 Xid Slot: 12, Wait Slot: 3, Task: 0x0000000006AF62C8, (Producer), Exchange Wait Type: e_waitPipeNewRow, Merging: 1
ResType:ExchangeId Stype:'AND' SPID:93 BatchID:0 ECID:19 TaskProxy:(0x00000001EFF24200) Value:0x6af62c8 Cost:(20/0)
SPID: 93 ECID: 19 Statement Type: SELECT Line #: 3
Input Buf: No Event:

Node:2
Port: 0x0000000151B5B430 Xid Slot: 13, Wait Slot: 2, Task: 0x00000002A46042C8, (Producer), Exchange Wait Type: e_waitPipeNewRow, Merging: 1
ResType:ExchangeId Stype:'AND' SPID:93 BatchID:0 ECID:21 TaskProxy:(0x00000001EFF242C0) Value:0xa46042c8 Cost:(20/0)
SPID: 93 ECID: 21 Statement Type: SELECT Line #: 3
Input Buf: No Event:

Node:3
Port: 0x00000003AD44BEE0 Xid Slot: 3, Wait Slot: 13, Task: 0x000000037C3782C8, (Consumer), Exchange Wait Type: e_waitPipeGetRow, Merging: 0
ResType:ExchangeId Stype:'AND' SPID:93 BatchID:0 ECID:9 TaskProxy:(0x000000022D837D90) Value:0x7c3782c8 Cost:(0/10000)
SPID: 93 ECID: 9 Statement Type: SELECT Line #: 3
Input Buf: No Event:

Node:4
Port: 0x000000018BB5F270 Xid Slot: 2, Wait Slot: 12, Task: 0x000000039612B948, (Consumer), Exchange Wait Type: e_waitPipeGetRow, Merging: 0
ResType:ExchangeId Stype:'AND' SPID:93 BatchID:0 ECID:11 TaskProxy:(0x000000022D837E50) Value:0x9612b948 Cost:(0/10000)
SPID: 93 ECID: 11 Statement Type: SELECT Line #: 3
Input Buf: No Event:
Back to top
View user's profile Send private message
Brian Donahue



Joined: 23 Aug 2004
Posts: 6674

PostPosted: Fri Jun 25, 2010 2:12 pm    Post subject: Reply with quote

Hello Jeroen,

SQL Response sets a trace flag on SQL Server that causes deadlock information to be written to the SQL Server's ERRORLOG, and then it reads the ERRORLOG to gather the output that you had quoted above.

I'm not sure how profiler and performance counters do this, but I would imagine that you have to set the trace flags to detect deadlocks there as well? For instance, DBCC TRACEON(1204) will put deadlock information into the SQL Server log.
Back to top
View user's profile Send private message
JeroenvH



Joined: 24 Jun 2010
Posts: 3

PostPosted: Fri Jun 25, 2010 6:31 pm    Post subject: Re: Reply with quote

Brian Donahue wrote:
Hello Jeroen,

SQL Response sets a trace flag on SQL Server that causes deadlock information to be written to the SQL Server's ERRORLOG, and then it reads the ERRORLOG to gather the output that you had quoted above.

I'm not sure how profiler and performance counters do this, but I would imagine that you have to set the trace flags to detect deadlocks there as well? For instance, DBCC TRACEON(1204) will put deadlock information into the SQL Server log.
I'll take a look at the errorlog if I find the deadlock there.

Since yesterday SQL-Response reported several more 'ghost' deadlocks and one actual deadlock (with an Victim spid) which also was trapped by profiler with an dead-lock graph.
Back to top
View user's profile Send private message
Brian Donahue



Joined: 23 Aug 2004
Posts: 6674

PostPosted: Sat Jun 26, 2010 9:38 am    Post subject: Reply with quote

Looks like your SQL Server is having a special kind of deadlock, an intra query parallel thread deadlock. The link has some information and some suggested workarounds.
Back to top
View user's profile Send private message
JeroenvH



Joined: 24 Jun 2010
Posts: 3

PostPosted: Mon Jun 28, 2010 10:27 am    Post subject: Reply with quote

Ah, thanks !

I'll look into it.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group