Specifies the transaction locking behavior for the connection.
Assembly: System.Data (in System.Data.dll)
|A different isolation level than the one specified is being used, but the level cannot be determined.|
When using OdbcTransaction, if you do not set or you set to Unspecified, the transaction executes according to the isolation level that is determined by the driver that is being used.
|The pending changes from more highly isolated transactions cannot be overwritten.|
|A dirty read is possible, meaning that no shared locks are issued and no exclusive locks are honored.|
|Shared locks are held while the data is being read to avoid dirty reads, but the data can be changed before the end of the transaction, resulting in non-repeatable reads or phantom data.|
|Locks are placed on all data that is used in a query, preventing other users from updating the data. Prevents non-repeatable reads but phantom rows are still possible.|
|A range lock is placed on the DataSet, preventing other users from updating or inserting rows into the dataset until the transaction is complete.|
|Reduces blocking by storing a version of data that one application can read while another is modifying the same data. Indicates that from one transaction you cannot see changes made in other transactions, even if you requery.|
The values are used by a .NET Framework data provider when performing a transaction.
The remains in effect until explicitly changed, but it can be changed at any time. The new value is used at execution time, not parse time. If changed during a transaction, the expected behavior of the server is to apply the new locking level to all statements remaining.
Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.