Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
adrian_const
Starting Member
1 Post |
 Posted - 2009-06-13 : 06:06:58
|
| Hi all,I encountered in our environment last day a very strange issue.We have a deadlock between processes accessing the same table; lets call it Sites.The strage thing is that according to the deadlock information from the Profiler; the resource involved in the deadlock is only one key of the PK index of the Sites table.Each process holds a Update lock on it(OwnerMode:U); one of the processes tries to upgrade this lock into a X(exclusive) and hence the deadlock.One of the processes is a SP executing an update on one of the fields; the other one is something like FETCHAPI_CURSOR0001001, indicating one of the VB applications accessing this table i guess.How can this be even possible; according to all Microsoft documentation never 2 processes can obtain an update lock in the same time,I appreciate any thoughts on this.Thanks,Adrian |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2009-07-18 : 16:27:35
|
The VB code may contain a transaction and the update cursor could be only a part of the code.
N 56°04'39.26"E 12°55'05.63" |
 |
|
|
|
|
|
strange deadlock