Why SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement

Why SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement

Postby jeroent » Tue 25 Nov 2008 14:28

Hi,

We are testing the dotConnect for Oracle provider if it is usable for our applications. So we have build a little test app with the trial version.
The test app is using the entity framework.

To see what this app is doing on the server we have traced the session on the database, to see what kind of querys the entity framework is creating.

there we saw the statement
SET TRANSACTION ISOLATION LEVEL READ COMMITTED
being fired from the test app.

Why is this statement fired? Transaction Isolation level is by default Read committed.....

thanks in advance

Jeroen
jeroent
 
Posts: 12
Joined: Tue 25 Nov 2008 13:41

Postby AndreyR » Wed 26 Nov 2008 13:02

We do this to guarantee Isolation Level will be necessary for our EDM Support. What kind of behaviour do you request?
AndreyR
Devart Team
 
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Postby jeroent » Wed 26 Nov 2008 13:42

We see this statement multiple times per session on the database. We would expect this statement only once per session. We see it before each DML statement and in our opinion this is unnecessary load on the server.
jeroent
 
Posts: 12
Joined: Tue 25 Nov 2008 13:41

Postby AndreyR » Wed 26 Nov 2008 14:47

Thank you for your feedback. We will investigate the possibility of changing this behaviour.
AndreyR
Devart Team
 
Posts: 2919
Joined: Mon 07 Jul 2008 13:16


Return to dotConnect for Oracle