implicit transactions

Hello,

 I've asked this question before, but the problem still persists, hence my question again:

Does Uniface use implicitly transactions? And can it be turned off?

Our DBA alerts us for the use of implicit transactions that degrade the performance of the application.

Here's a piece of the sql logging:

 

 

In the source where this select statement occurs, there is no a commit or rollback.

Is it necessary to do commit/rollback after select?

Best regards,
Erhan

------------------------------
Erhan Gunbulut
Sogeti Nederland B.V.
------------------------------

Hello Erhan,

As I have already replied in the other post (Implicit transactions) the mentioned behavior seems to be caused by the Microsoft ODBC driver. Here is, once more, the question that one of my colleagues has raised on the SQL Server Forum (back in 2017):

• In manual commit mode, SQLEndTran() starts a new transaction

My colleague has replicated this behavior also outside of Uniface.

I had a another look at the old case that is related to the above mentioned post and my colleague suggested the following workarounds to the customer that has originally reported this behavior:

1. Use the (old) SQL ODBC driver instead of the (newer) SQL Server Native Client ODBC driver or the ODBC Driver for SQL Server, or
2. Explicitly close the MSS path as a workaround.

In both cases my colleague could not see any implicit transactions anymore.

I hope this helps.

Kind regards

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------