Assembly: System.Data (in system.data.dll)
|Chaos||The pending changes from more highly isolated transactions cannot be overwritten.|
|ReadCommitted||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.|
|ReadUncommitted||A dirty read is possible, meaning that no shared locks are issued and no exclusive locks are honored.|
|RepeatableRead||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.|
|Serializable||A range lock is placed on the DataSet, preventing other users from updating or inserting rows into the dataset until the transaction is complete.|
|Snapshot||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.|
|Unspecified||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 IsolationLevel or you set IsolationLevel to Unspecified, the transaction executes according to the default isolation level of the underlying ODBC driver.
The IsolationLevel values are used by a .NET Framework data provider when performing a transaction.
The IsolationLevel 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 98, Windows Server 2000 SP4, Windows CE, Windows Millennium Edition, Windows Mobile for Pocket PC, Windows Mobile for Smartphone, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter EditionThe Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.