SaveChanges
uses implementation of DbTransaction
for current store provider. It means that default transaction isolation level is set to default value for the database server. In SQL Server it is READ COMMITTED
. If you want to change isolation level you can use TransactionScope
. You can also override SaveChanges
in your derived context and wrap base.SaveChanges()
to the scope directly in overriden method.
public override void SaveChanges()
{
// Default isolation level for TransactionScope is Serializable
using (var scope = new TransactionScope())
{
base.SaveChanges();
scope.Complete();
}
}
You can further improve this code to allow you passing isolation level to SaveChanges
etc. Once you start changing isolation levels you should do it consistently. It means you should define isolation level each time you want to run a transaction because isolation level is configured per connection and connections are reused when using connection pooling.
Edit: Default transaction level in EF6 has changed to READ COMMITTED SNAPSHOT
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…