Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.ms-sqlserver > #584

Re: help needed understanding a deadlock

Show all headers | View raw

migurus (migurus@yahoo.com) writes:
> UPDATE PR_CUST SET PR_RUN_ID = NULL
> WHERE CUST_ID IN (select tid from @IDS)
>... 
> I can not identify which resources specifically were the culprit. Does
> the trace shows a page, or some other resource that was a center of
> deadlock?
 
It seems that both processes has a shared lock on the table, and then asks 
for an Intent-Exclusive whereupon they clash. This is a bit strange, since 
they should take out an Update lock instead; only one proecss at a time can 
only an Update lock on a resource.

But what indexes are there on this table? It seems that this table is a
heap (:0 in the object address.) Is there an index on CUST_ID?

-- 
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Find similar

Thread

help needed understanding a deadlock migurus <migurus@yahoo.com> - 2011-08-02 19:56 -0700
  Re: help needed understanding a deadlock Erland Sommarskog <esquel@sommarskog.se> - 2011-08-03 23:21 +0200

csiph-web