Hello all,

I have an application that uses a connectionpool with connections to
SQLServer2000 through the MS JDBC driver, current version.

The writes are very basic and so they are mostly done in autocommit mode. In
one location where a set of rows read from a tabular source like Excel are
updated-by-id or inserted when not found. In a second table a record is
inserted also for each row inserted in the primary table. To find the
foreign key a select on the primary table is performed first.

All selects, updates etc. are using the same connection. Recently we decided
to speed up the process by setting the connection to autocommit(false) and
doing a commit() for each K records and at the end of the process.

To our surprise one server (obviously not one of our own but one of our
clients) started suffering from deadlocks. It was completely up to date and
had all service packs installed (some of ours didn't, some did). We backup
up the databse and restored it on one of our servers. Off course, the
problem could not be reproduced.

I decided to revert to autocommit mode and the problems disappeared.

Does anyone have an idea of what could cause this behaviour?

Running the same code on Oracle and MySQL showed no problems, BTW.

Regards,

Silvio Bierman