Problem with deadlocks

My application is being concurrently used by 11 people and over a course of 30 minutes and 800 plus transactions we experienced 84 deadlocks. The application is coded so that the users can retry transactions without losing any data, but they are complaining that the deadlocks occur too often.

The application has 5 different types of transactions, 3 which do a mix of read/write operations and 2 which only do read operations. The database has 9 tables, 8 with primary key constraints, and 1 with an alternate key index. The table that doesn't have a primary key constraint is used for auditing.

The deadlocks used to be more frequent, but I analyzed and changed the transactions to ensure that they all access tables in the same sequence and that brought the deadlock frequency count down some.

What else can I do to bring the deadlock frequency count down more? Received on Fri Jan 19 2001 - 15:35:03 CST