Deadlocks

[Ben Spigle]

Is there any way to totally avoid deadlocks. In some critical applications
we have removed transactions entirely, counting on other means to maintain
database consistency. We still get deadlocks in this area. These are mainly
inserts, and the only thing I can think is that updates to the indexes are
causing multiple page locks which result in deadlocks. Is this true?

Will deadlocks be eliminated in 7.0 with row level locking for this situation?
Or will index page splits still cause a possibility of deadlock contention?

Thanks!
ben

[mscoyle]

Try creating a clustered index on the tables which
are getting insert deadlocks. It doesn't matter
which columns are in the index, just make sure that
the tables have one.




On 12/17/98 6:15:05 PM, Ben Spigle wrote:
>
Is there any way to totally avoid deadlocks. In some critical
> applications
we have removed transactions entirely, counting on other
> means to maintain
database consistency. We still get deadlocks in this
> area. These are mainly
inserts, and the only thing I can think is that
> updates to the indexes are
causing multiple page locks which result in
> deadlocks. Is this true?

Will deadlocks be eliminated in 7.0 with row
> level locking for this situation?
Or will index page splits still cause a
> possibility of deadlock contention?

Thanks!
ben

[Ben Spigle]

On 12/18/98 3:28:43 PM, mscoyle wrote:
> Try creating a clustered index on the tables which
are getting insert
> deadlocks. It doesn't matter
which columns are in the index, just
> make sure that
the tables have one.




Thanks for the reply. The table in question already has a clustered
index. The table is the order detail line table and the clustered index
is on the item code.

ben