How to avoid SET ISOLATION LEVEL READ COMMITTED calls

mars · Post by **mars** » Fri 06 May 2011 13:34

Our program use dotConnect for Oracle, and today I get following feedback from Oracle guru:
"
Found 173.571 calls SET TRANSACTION ISOLATION LEVEL READ COMMITTED. The READ COMMITTED setting is the default Oracle Database transaction behavior. If the transaction contains DML that requires row locks held by another transaction, then the DML statement waits until the row locks are released.
I STRONGLY recommend to remove with calls.
"

Is it possible to remove this calls from dotConnect source code or make it optional?

Personally, I do not think that this somehow affects Oracle performance, but is obliged to respond to oracle dba inquiries.

Thanks in advance

Shalex · Post by **Shalex** » Wed 11 May 2011 14:27

Thank you for your suggestion. We will investigate the possibility of excluding this call after every transaction opening.

Shalex · Post by **Shalex** » Wed 18 May 2011 16:06

The issue with redundant setting isolation level to READ COMMITTED on every transaction opening is fixed. I will post here when the corresponding build of dotConnect for Oracle is available for download.

Shalex · Post by **Shalex** » Thu 02 Jun 2011 11:49

New build of dotConnect for Oracle 6.30.165 is available for download!
It can be downloaded from http://www.devart.com/dotconnect/oracle/download.html (trial version) or from Registered Users' Area (for users with valid subscription only): http://secure.devart.com/ .
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=21148 .