Isolation Levels in SQLOLEDB
Microsoft® SQL Server™ 2000 clients can control transaction-isolation levels for a connection. To control transaction-isolation level, the SQLOLEDB consumer uses:
- DBPROPSET_SESSION property DBPROP_SESS_AUTOCOMMITISOLEVELS for SQLOLEDB default autocommit mode.
The SQLOLEDB default for the level is DBPROPVAL_TI_READCOMMITTED.
- The isoLevel parameter of the ITransactionLocal::StartTransaction method for local manual-commit transactions.
- The isoLevel parameter of the ITransactionDispenser::BeginTransaction method for MS DTC-coordinated distributed transactions.
SQL Server 2000 allows read-only access at the dirty read isolation level. All other levels restrict concurrency by applying locks to SQL Server 2000 objects. As the client requires greater concurrency levels, SQL Server 2000 applies greater restrictions on concurrent access to data. To maintain the highest level of concurrent access to data, the SQLOLEDB consumer should intelligently control its requests for specific concurrency levels.