May 11, 2008 at 7:46 pm
Does anyone know what message will we get when an internal deadlock occurs during parallel processing in SQL server 2005. I have taken care in my code to retry the the transaction after a delay period if a deadlock occurs.
However , now I have realised that the deadlock can also during parallel processing in sq server. I wanted to know what would be the error message we will recieve if deadlock occurs.. is it the same as
' Transaction (Process ID NO.) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction. '
Thanks,
May 12, 2008 at 2:56 am
I'm getting "Transaction (Process ID 76) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction." too.
-------------------------
- Name?
- Abu Dalah Sarafi.
- Sex?
- 3 times a week!
- No, no. Male or Female?
- Male, female, sometimes camel...
May 12, 2008 at 6:59 am
Regardless of cause, that's the error you get for deadlocks.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
May 12, 2008 at 8:27 am
Add a MAXDOP 1 hint to the query to prevent parallelism. There is a potential performance hit, but if the query is failing, the performance hit from the MAXDOP is still a better result.
Look for CXPACKET waits in SSMS Activity Monitor, or through sys.dm_os_wait_stats (http://msdn.microsoft.com/en-us/library/ms179984.aspx) to determine if you are actually suffering from parallelism related issues.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply