Strange database deadlock

[Maggie Pong]

Hi,

I had a deadlock situation on SQLServer 2000. When I look at the
Locks / process ID screen on Enterprise Manager, for one of the
session, I see the object being one table and the index is on another
totally unrelated table's primary key. This is really odd since there
are no foreign keys tying these two tables together. They don't even
reference the same parent tables. These two tables are quite
dis-joint. Does anyone know why I will get this kind of lock?

Thanks,

Maggie :)

[Alexey Aksyonenko]

Maggie - run DBCC CHECKDB (msdb) to make sure you don't have
structural issues. Other than that - verify that the 2 really aren't
related somewhere.
mp*********@yahoo.com (Maggie Pong) wrote in message news:<a3**************************@posting.google. com>...

Hi,

I had a deadlock situation on SQLServer 2000. When I look at the
Locks / process ID screen on Enterprise Manager, for one of the
session, I see the object being one table and the index is on another
totally unrelated table's primary key. This is really odd since there
are no foreign keys tying these two tables together. They don't even
reference the same parent tables. These two tables are quite
dis-joint. Does anyone know why I will get this kind of lock?

Thanks,

Maggie :)

[Erland Sommarskog]

[posted and mailed, please reply in news]

Maggie Pong (mp*********@yahoo.com) writes:

I had a deadlock situation on SQLServer 2000. When I look at the
Locks / process ID screen on Enterprise Manager, for one of the
session, I see the object being one table and the index is on another
totally unrelated table's primary key. This is really odd since there
are no foreign keys tying these two tables together. They don't even
reference the same parent tables. These two tables are quite
dis-joint. Does anyone know why I will get this kind of lock?

The tables may have been accessed in the same user-defined transaction.

Now, if you say that these two tables are not accessed in the same
transaction anywhere in the system - or at least should not be, this
could be an indication that you have transactions that you fail to
commit. There are a couple of nasty ways where this could happen in
conjunction with command timeouts in client code, or some errors in
stored procedures.

--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp