Read committed isolation using row versioning is enabled by setting the read committed snapshot database option on 将read _ committed _ snapshot数据库选项设置为on可启用使用行版本控制的已提交读隔离。
All concurrency side effects can happen in read uncommitted , but there is no read locking or versioning , so overhead is minimized 未提交读可能发生所有的并发副作用,但是由于无需读取锁定或读取版本,因此开销达到最小化。
All of the concurrency side effects can happen in read uncommitted , but there is no read locking or versioning , so overhead is minimized 在未提交读中,所有并发副作用都可能发生,但因为没有读取锁定或版本控制,所以开销最少。
There is one row for each transaction that is running under snapshot isolation level , or read - committed isolation level that is using row versioning 在快照隔离级别或使用行版本控制的已提交读隔离级别下运行的每一个事务都占有一行。
Row versions that are generated by data modification transactions in a database that uses snapshot or read committed using row versioning isolation levels 由使用已提交读快照隔离或快照隔离级别的数据库中的数据修改事务生成的行版本。
Row versions that are generated by data modification transactions in a database that uses read - committed using row versioning isolation or snapshot isolation transactions 由使用已提交读的快照隔离或快照隔离事务的数据库中数据修改事务生成的行版本。
When the read committed snapshot database option is set on , read committed isolation uses row versioning to provide statement - level read consistency 将read _ commited _ snapshot数据库选项设置为on时,已提交读隔离使用行版本控制提供语句级别的读取一致性。
Heap - optimized bulkload operations with concurrent scan , under these isolation levels : snapshot , read uncommitted , and read committed using row versioning Hobt . bulk _ operation下列隔离级别下的优化堆大容量加载操作与并发扫描:快照、未提交读和使用行版本控制的已提交读。
With an exclusive lock , no other transactions can modify data ; read operations can take place only with the use of the nolock hint or read uncommitted isolation level 使用排他锁( x锁)时,任何其他事务都无法修改数据;仅在使用nolock提示或未提交读隔离级别时才会进行读取操作。
When the read committed snapshot database option is set off , which is the default setting , read committed isolation behaves as it did in earlier versions of sql server 将read _ commited _ snapshot数据库选项设置为off (默认设置)时,已提交读隔离的行为与在sql server的早期版本中相同。