|
|
Posted by Marco van de Voort on 10/02/44 11:48
On 2006-05-23, Erland Sommarskog <esquel@sommarskog.se> wrote:
> Marco van de Voort (marcov@stack.nl) writes:
>>> To wit, if a query times out, and there is a transaction in progress,
>>> the transaction is not rolled back automatically. It is irrelevant
>>> whether the transaction was started prior to the submission of the
>>> query batch, or started within the query batch that timed out.
>>>
>>> The application must handle this by submitting
>>>
>>> IF @@trancount > 0 ROLLBACK TRANSACTION
>>
>> I call the rollback of the relevant ADO connection on the exception caused
>> by the timeout.
(for the record: I already did this all the time, it is not a change)
> So, did you investiagate if you have any blocking?
It occurs less than once a month (unfortunately on a painful moment). IOW, I
can't reproduce it at will. Which is why I asked if sb recognized the
problems.
> Also, I have you examined the SQL Server error log?
Yes, nothing. But maybe my logging settings are wrong.
Navigation:
[Reply to this message]
|