IsolationLevel Type
Transaction isolation level for database operations. Corresponds to the System.Transactions.IsolationLevel but provides SQL provider specific functionality. Only applied when SubmitUpdates creates its own (standalone) write transaction; if you wrap your own ambient System.Transactions scope, that scope's isolation level is used instead.
Record fields
| Record Field |
Description
|
|
Allows any level of isolation, including overlapping changes (SQL Server specific)
|
|
Special value to indicate that no transaction should be created
|
|
Prevents dirty reads but allows non-repeatable reads and phantom reads. (This describes the default isolation of most DB *engines* - it is NOT SQLProvider's default; TransactionOptions.Default is Serializable, inherited from System.Transactions.)
|
|
Allows dirty reads, non-repeatable reads, and phantom reads (fastest but least safe)
|
|
Prevents dirty reads and non-repeatable reads, but phantom reads can occur
|
|
Highest isolation level - transactions are completely isolated from each other
|
|
SQL Server specific - provides statement-level read consistency using versioning
|
|
Use the default isolation level of the database
|