Subject Database deadlock
Author jensdein

I have a database where I use one transaction (cuncurrent isolation)
for editing and another (Committed isolation) for searching.

Sometimes my simple select query that I use for searching for
customers generates a deadlock error.

I was of the impression that this actually should't happen on a select
statement. I have tried to trace the SQL to see if some other SQL was
executed that I was unaware of, that might have caused the deadlock -
but there wasn't.

Earlier I used a transaction isolation of Committed also on those
datasets the were updatable and back then I diden't seem to have this

Does anyone have a clue what the problem might be?

I use IBO objects for database connectivity.