Question about TransactionScope behavior

doublebow · Post by **doublebow** » Thu 12 Aug 2010 00:25

Hi There,

I have been evaluating dotConnect for Oracle for a few weeks now. Excellent product. I have a particular question about the behavior of TransactionScope and what is seens in DBMonitor. If someone can clarify this, that will be much appreciated.

1. I do not see any specific ROLLBACK or COMMIT statements being executed on the database. So how is this accomplished, or are they simply not visible on DBMonitor?

2. As per this post (http://www.devart.com/blogs/dotconnect/?p=403), DataContext is instructed to create only one connection, but in DBMonitor I can see multiple connection -why is this so?
Code: Select all
```
Devart.Data.DataContext.MaxUsedConnections = 1 
```
3. How is the transaction, then, commited or rollbacked on multiple connections?

StanislavK · Post by **StanislavK** » Fri 13 Aug 2010 17:03

Concerning your questions:

1. We will analyze the situation and inform you about the results.

2. The MaxUsedConnections property affects queries only, update/insert/delete commands use a new connection each time they are executed anyway.

3. This is possible since Oracle server supports two-phase commit. For details, please refer to the documentation on distributed transactions:
http://msdn.microsoft.com/en-us/library/ms681205.aspx
http://download.oracle.com/docs/cd/A976 ... s.htm#7171

StanislavK · Post by **StanislavK** » Fri 24 Sep 2010 16:44

We've implemented the possibility of tracing distributed transactions in dbMonitor. This functionality is available in the new 5.70.170 build of dotConnect for Oracle. It can be downloaded from
http://www.devart.com/dotconnect/oracle/download.html
(the trial version) or from Registered Users' Area (provided that you have an active subscription):
http://secure.devart.com/

The detailed information about the fixes and improvements implemented in dotConnect for Oracle 5.70.170 is available at
http://www.devart.com/forums/viewtopic.php?t=19068