Is it safe to enable MSDTC (Microsoft Distributed Transaction Coordinator) on our server?

I always worry about using two instances DbContextthat require a distributed transaction coordinator, especially when I use a type library SimpleMembershipthat has its own database connection.

This problem is always a problem in my case. For example, I use a SimpleMembershipprovider for user accounts of applications, and I want to save a user with additional information, for example, a company. Therefore, without MSDTC permission, I cannot do this inside a transaction. Thus, it is possible that inconsistent data is inserted into the database.

So my question is: should I worry about this problem and try to find a better solution, or can I just turn on MSDTC on my server and not worry about it? Are there any implications of enabling MSTDC?

Thanks!

+4
source share

All Articles