|
Posted by pb648174 on 05/17/06 23:34
If an instance of SQL 2005 was in use and was using row versioning,
under what circumstances would the below error occur?
Transaction (Process ID 56) was deadlocked on lock resources with
another process and has been chosen as the deadlock victim. Rerun the
transaction
We used to get this sort of thing when a large copy process was running
under a transaction, but all it was doing was reading the records and
creating brand new records yet would still lock the entire table. Once
we enabled the row versioning, we stopped having this issue, but it
seems that there are some circumstances in which it still happens, i.e.
the above error.
Any ideas how that might occur?
Navigation:
[Reply to this message]
|