StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13724167
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-05T13:18:33.813
FavoriteCount
0
LastActivityDate
2012-12-05T13:18:33.813
LastEditDate
LastEditorUserId
0
OwnerUserId
1193333
ParentId
12688197
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I have just tried how escalation to distributed transaction behaves in SQL Server 2012 (EXPRESS). And I have observed the same behaviour as for SQL Server 2008. I have tested it on very simple code with <code>SqlConnection</code> objects. There are always two database access (INSERTs) in one transaction scope. Not nested connections - NOT ESCALATING This is the only option if you want to avoid the promotion to DTC. Access only one durable resource (database) during the transaction and closing one connection before opening another. (Eventually you can avoid DT by reusing the same connection but it is not necessary when you use Connection pooling and would probably make your code less readable.) <pre><code>static string connectionString = "data source=.\\;Integrated Security=SSPI;Database=TestDB"; static void Main(string[] args) { using (var scope = new TransactionScope()) { using (var conn = new SqlConnection(connectionString)) { conn.Open(); using (var command = conn.CreateCommand()) { command.CommandType = CommandType.Text; command.CommandText = "INSERT INTO TestTable(Value) VALUES (@1)"; command.Parameters.Add(new SqlParameter("1", "123456")); command.ExecuteNonQuery(); } } using (var conn2 = new SqlConnection(connectionString)) { conn2.Open(); using (var command2 = conn2.CreateCommand()) { command2.CommandType = CommandType.Text; command2.CommandText = "INSERT INTO TestTable(Value) VALUES (@1)"; command2.Parameters.Add(new SqlParameter("1", "123456")); command2.ExecuteNonQuery(); } } scope.Complete(); } } </code></pre> Nested connections - ESCALATING <pre><code>static string connectionString = "data source=.\\;Integrated Security=SSPI;Database=TestDB"; static void Main(string[] args) { using (var scope = new TransactionScope()) { using (var conn = new SqlConnection(connectionString)) { conn.Open(); // EXECUTE INSERT using (var conn2 = new SqlConnection(connectionString)) { conn2.Open(); // EXECUTE INSERT } } scope.Complete(); } } </code></pre> Not nested connections accessing different databases - ESCALATING If you access two or more durable resources during the transaction it will be always promoted to DTC. <pre><code>static string connectionString = "data source=.\\;Integrated Security=SSPI;Database=TestDB"; static string connectionString2 = "data source=.\\;Integrated Security=SSPI;Database=TestDB2"; static void Main(string[] args) { using (var scope = new TransactionScope()) { using (var conn = new SqlConnection(connectionString)) { conn.Open(); // EXECUTE INSERT } using (var conn2 = new SqlConnection(connectionString2)) { conn2.Open(); // EXECUTE INSERT } scope.Complete(); } } </code></pre> Note It does not matter what kind of CRUD operation you will execute, it always depends in which manner the connections are opened and closed.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing TransactionScope in SQL Server 2012
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmipe34
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsing TransactionScope in SQL Server 2012
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.