|
|
|
Microsoft OLE DB Provider for SQL Server error '80004005'
Technical Note USA9613
Created 20-Nov-2003
Applies To
DATABridge MS-SQL Server Client for NT 4.0 4.0
Symptoms
Microsoft OLE DB Provider for SQL Server error '80004005'Error: " Your transaction (process ID #13) was deadlocked with another process and has been chosen as the deadlock victim"
Fix
Deadlock resolution is a normal function of SQL Server. When a transaction from one user blocks a transaction from another user and the second user is also blocking a transaction being requested by the first user, it creates a stalemate or "deadlock" between two processes. When this happens, SQL Server will resolve the conflict by randomly selecting one of the two processes to cancel. The owner of this cancelled transaction is considered the "deadlock victim." The resolution is simply to refresh the page or rerun the report and it will very likely go through.Typically deadlocks occur infrequently. Two deadlocks occurring within one week is not cause for alarm, but it does indicate that there was probably heavier than normal processing of some sort going on (perhaps end-of-month activity??). If a pattern of deadlocks begins to show, the database administrator should set up some performance monitoring traces for the suspected time period. Then if a deadlock occurs, we will have the information to analyze the activity on the server and tune it as needed.
