Linq2SQL: SubmitChanges covered by a transaction?

Question

MyDataContext context = new MyDataContext();

// do a lot of insert, deletes and updates

context.SubmitChanges();

Will all SQL genereated and executed by SubmitChanged() be covered by a transaction? How do I make sure it's covered by a transaction?

Updated:

The reason why I asking it that I having a weird bug where I suspect a transaction hasn't been used.

The procedure is about 500 inserts and a final update on one record. Sometimes the update (and perhaps a few of the insert...) isn't registered in the database.

(SQL Transactions isn't shown in my debug output?)

http://stackoverflow.com/questions/542525/transactionscope-vs-transaction-in-linq2sql See the answer with the most votes. The accepted answer doesn't tell the whole story. — Ben Lesh, Sep 17 '09 at 14:34

score 4 · Accepted Answer · answered Sep 17 '09 at 11:23

4

it is, and the whole thing will roll back if it fails

How to: Submit Changes to the Database (LINQ to SQL)

answered Sep 17 '09 at 11:23

Ahmed Khalaf

1,190
11
28

score 3 · Answer 2 · answered Sep 17 '09 at 12:09

3

If you want everything to happen within a transaction use a Transaction Scope

http://msdn.microsoft.com/en-us/library/system.transactions.transactionscope.aspx

answered Sep 17 '09 at 12:09

Shiraz Bhaiji

62,289
31
137
240

Linq2Sql will create a transaction for you, no need to throw the confusion of TransactionScope in the mix. – Michael Hart Sep 17 '09 at 13:17
1

+1. TransactionScope simplifies code a bit as it doesn't require a try catch block for a Rollback. – Ben Lesh Sep 17 '09 at 14:41

score 2 · Answer 3 · answered Sep 17 '09 at 14:14

2

Explicitly creating a TransactionScope is only needed when you are invoking SubmitChanges multiple times and want all of the invokations to be included in one single transaction.

answered Sep 17 '09 at 14:14

Konamiman

48,742
16
110
136

Linq2SQL: SubmitChanges covered by a transaction?

3 Answers3