.net - Side effects of enabling DTC in SQL Server -


i have large legacy database in dtc disabled , need enable use transaction isolation level "read uncommitted", i'm afraid of side effects of enabling it.

this needed specific query , won't used anywhere else.

does know if bring problems on existing legacy systems?


details:

i'm trying use transactionscope in .net application isolation level "read uncommitted" in order not lock query. query searches register locked in database transaction of application.

maybe there way working without changing configuration of dtc. appreciated!

transactionscope automatically promote/enlist transaction distributed transaction needed, requires msdtc running , configured. remove dependency on msdtc isolated queries, try 1 of following:

  • use sqltransaction system.data.isolationlevel.readuncommitted
  • execute set transaction isolation level read uncommitted query on connection before running queries
  • specify nolock locking hint in queries

note read uncommited result in dirty reads (including missed or duplicated data) should used in cases concurrency benefits outweigh data integrity. alternative turn on read_committed_snapshot database option row versioning instead of locking used provide integrity in default read committed isolation level. see read committed snapshot vs snapshot isolation level.


Comments