system.transactions | 易学教程

Inner TransactionScope with different IsolationLevel, how can it be achieved?

阅读更多关于 Inner TransactionScope with different IsolationLevel, how can it be achieved?

问题 The current implementation of TransactionScope lacks the ability to change IsolationLevels in nested scopes. MSDN states: When using nested TransactionScope objects, all nested scopes must be configured to use exactly the same isolation level if they want to join the ambient transaction. If a nested TransactionScope object tries to join the ambient transaction yet it specifies a different isolation level, an ArgumentException is thrown. However SQL Server allows us to change Isolation Levels

TransactionScope throws TransactionAbortedException when Disposed

阅读更多关于 TransactionScope throws TransactionAbortedException when Disposed

问题 I have the following scenario: Parent process start TransactionScope, a token identifying the transaction is created using TransactionInterop.GetTransmitterPropagationToken, inserts data to database. TransactionScope completes. Another process is started, using the above mentioned token it creates Transaction which is then used to create TransactionScope. This process also inserts data to database. TransactionScope completes and is disposed. Parent process tries to dispose its

TransactionScope throws TransactionAbortedException when Disposed

阅读更多关于 TransactionScope throws TransactionAbortedException when Disposed

SqlClient.SqlTransaction vs System.Transactions

阅读更多关于 SqlClient.SqlTransaction vs System.Transactions

问题 We have some constant issues with MSDTC setting up, now considering replacing SystemTransactions with SqlTransactions . I am interested in differences of the above, and possible issues we might have doing that. 回答1: The article quoted and referenced by Massimiliano was 7 years old when referenced and therefore refers only to .NET 2.0 and SQL Server 2000 and 2005. However, I believe the salient points are still valid for later versions. I'm having trouble finding directly applicable commentary

.net durable resource manager for transactional filesystem access

阅读更多关于 .net durable resource manager for transactional filesystem access

问题 I'm trying to wrap my head around the use of the System.Transactions namespace in C#. I've found some documentation on MSDN regarding using resource managers, but it only covers volatile, in-memory resource managers in any detail (like Transactional ). I'm basically looking for something that I can use inside of a TransactionScope, just like Transactional<> but use it for writing/modifying/deleting files on disk. Does something like this exist in the standard libs? I've read that NTFS has

SQL CE 4 System.Transaction support

阅读更多关于 SQL CE 4 System.Transaction support

问题 A similar question was asked here but had no answer. I am attempting to use a System.Transactions.CommittableTransaction with EF CTP4 and SQL CE 4. I have created the following transaction attribute for my ASP.NET MVC Controller actions: public class TransactionAttribute : ActionFilterAttribute { CommittableTransaction transaction; public override void OnActionExecuting(ActionExecutingContext filterContext) { transaction = new CommittableTransaction(); Transaction.Current = transaction; base

Using transactions across processes

阅读更多关于 Using transactions across processes

问题 I'm trying to use System.Transactions (TransactionScope) to coordinate a set of processes, each of which does some database work. Ultimately all processes need to commit or be rolled back atomically via one parent process. Unfortunately, nothing I've tried so far works. My basic strategy is to TransactionScope in the parent process, save it to a file, and invoke a child process, which loads the file, uses the transaction inside its own TransactionScope, and returns to the parent. But this

Trace why a transaction is escalated to DTC

阅读更多关于 Trace why a transaction is escalated to DTC

问题 Is there any way to determine precisely why a System.Transaction TrasactionScope is being escalated to the DTC? We are hitting a bump with one of our components that seem to escalate the transaction while all other components (which seem deceptively similar) does not do escalation. Are any information made available on the reasons for the escalation and how can they be found and observed? SQL Profiler? Log files? Or am I out of luck on this one? UPDATE: I'm running against SQL Server 2005 for

TransactionScope across AppDomains and processes

阅读更多关于 TransactionScope across AppDomains and processes

问题 Is it real to use System.Transactions (primarily TransactionScope) across different AppDomains and processes? DependentTransaction works only inside one AppDomain. 回答1: Yes, it works. We are flowing transactions via WCF, calling out of process transactional COM+ components, and manually passing transactions from a .NET 2.0 asmx web service to a WCF service. Now that is not to say that the setup is not finicky. I think most of the issues were around getting MSDTC set up properly on all the

TransactionScope across AppDomains and processes

阅读更多关于 TransactionScope across AppDomains and processes

Is it real to use System.Transactions (primarily TransactionScope) across different AppDomains and processes? DependentTransaction works only inside one AppDomain. Yes, it works. We are flowing transactions via WCF, calling out of process transactional COM+ components, and manually passing transactions from a .NET 2.0 asmx web service to a WCF service. Now that is not to say that the setup is not finicky. I think most of the issues were around getting MSDTC set up properly on all the servers. UPDATE We don't use DependentClone . We are passing the transaction as a byte array using