R
Rene
Hi,
I've read some articles about this issue but no answer found.
Once in some weeks we get a timeout exception on a commit. The command
timeout is 30 seconds, but this error occurs 11 seconds after we write the
data to the database.
The commit transaction failes and the catch block try to rollback the
transaction, but this gives an exception too.
So from our logs we see:
00:00 StartTransaction()
00:00 Write record in table 1
00:01 Write record in table 2
00:12 Commit exception (timeout)
00:12 Rollback exception (transaction already completed)
It is not logical for me why a connection with 30 seconds timeout can
timeout after 10 seconds.
I read other used expierenced the same problem. The only explantion I have
is SQL 2000 is enlarging the database files with 10% autogrow.
TIA,
Rene
I've read some articles about this issue but no answer found.
Once in some weeks we get a timeout exception on a commit. The command
timeout is 30 seconds, but this error occurs 11 seconds after we write the
data to the database.
The commit transaction failes and the catch block try to rollback the
transaction, but this gives an exception too.
So from our logs we see:
00:00 StartTransaction()
00:00 Write record in table 1
00:01 Write record in table 2
00:12 Commit exception (timeout)
00:12 Rollback exception (transaction already completed)
It is not logical for me why a connection with 30 seconds timeout can
timeout after 10 seconds.
I read other used expierenced the same problem. The only explantion I have
is SQL 2000 is enlarging the database files with 10% autogrow.
TIA,
Rene