How to run two Entity Framework Contexts inside TransactionScope without MSDTC?

entity-framework msdtc transactions


This problem is not readily reproducible in a simple example here but was wondering if anyone has any experience and tips, here is the issue:

  • using Entity Framework
  • have many points in application where (1) data is written to some entity table e.g. Customer, (2) data is written to history table
  • both of these actions use Entity Framework, HOWEVER, they use different contexts
  • these actions need to be both in one transaction: i.e. if one fails to write, the other should not write, etc.
  • I can wrap them with a TransactionScope,

like this:

using (TransactionScope txScope = new TransactionScope()) {

but this gives me:

Microsoft Distributed Transaction Coordinator (MSDTC) is disabled for network transactions.

Our database admin has told me that MSDTC is disabled by choice and can not be installed.

Hence I am making changes trying to create my own EntityConnection with a MetadataWorkspace with the idea that each context will use the same EntityConnection. However, this is proving near impossible trying to get it to work, e.g. currently I continue to get the above error even though theoretically both contexts are using EntityConnection. It's difficult to understand where/why Entity Framework is requiring the MSDTC for example.

Has anyone gone down this road before, have experience or code examples to share?

9/13/2018 9:05:10 PM

Accepted Answer

Well, the problem is quite easy.

If you are using sql server 2008 you should not have that problem because you have promotable transaction, and as .NET knows that you are using the same persistence store (the database) it wont promote it to DTC and commit it as local. look into promotable transaction with sql server 2008.

As far as I know Oracle is working in its driver to support promotable transactions, but I do not know the state, MS oracle driver does not support it.

If you are using a driver that do not support promotable transactions it is impossible for .NET to use local transaction doing two connections. You should change your architecture or convince the database admin for installing MSDTC.

8/13/2014 10:27:52 AM

Popular Answer

I think that what you need to do is to force your contexts to share single database connection. You will be able then to perform these two operations against two different contexts in single transaction. You can achieve this by passing one EntityConnection object to both of your context's constructors. Of course this approach will require you to pass this object to methods which update DB.

I have recently blogged about creating database context scope which will make using multiple EF contexts and transactions easier.

Related Questions


Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow