您要查找的是不是：
- Use the appropriate isolation level. 使用合适的隔离级别。
- SET TRANSACTION ISOLATION LEVEL SERIALIZABLE Begin Transaction. 在事务开始之前加上设置事务的级别
- The query is executed at the current isolation level. 查询在当前隔离级别上执行。
- Always use transaction isolation level set to Serializable. 总是将事务隔离级别设置为序列的。
- Transaction isolation level is set as a property of the Connection object. 事务隔离级别是作为Connection对象的属性设置的。
- Isolation level with which the transaction for this request is created. 创建此请求的事务时所用的隔离级别。
- With one exception, you can switch from one isolation level to another at any time during a transaction. 在事务进行期间,可以随时将事务从一个隔离级别切换到另一个隔离级别,但有一种情况例外。
- For an example in which the isolation level is changed in the middle of a transaction, see Phantom row tutorial. 有关在事务中间更改隔离级别的示例,请参见幻像行教程。
- XA distributed transaction connections default to the Read Committed isolation level. XA分布式事务连接默认使用“提交读”隔离级别。
- However, you can change a transaction started in SNAPSHOT isolation to any other isolation level. 但是,可以将在SNAPSHOT隔离中启动的事务更改为任何其他隔离级别。
- The ability of a cursor to detect changes is also influenced by the transaction isolation level. 游标检测这些变化的能力也受事务隔离级别的影响。
- The isolation level under which a Transact-SQL statement executes determines its locking and row versioning behavior. 执行Transact-SQL语句所使用的隔离级别确定其锁定行为和行版本化行为。
- Locking a range of keys allows transactions running at the serializable isolation level to prevent phantom inserts and deletes. 锁定某个范围内的键,使事务可以运行在可序列化隔离级别,防止假插入和假删除。
- To determine the transaction isolation level currently set, use the DBCC USEROPTIONS statement as shown in the following example. 若要确定当前设置的事务隔离级别,请使用DBCC USEROPTIONS语句,如下面的示例所示。
- For more information on isolation levels, see Isolation levels and consistency. 有关隔离级别的详细信息,请参见隔离级别和一致性。
- Is MySQL Cluster transaction-safe? What isolation levels are supported? MySQL集群是事务安全的吗?它支持什么样的事务隔离级别?
- A transaction cannot be set to SNAPSHOT isolation level that started with another isolation level; doing so will cause the transaction to abort. 不能将通过其他隔离级别开始的事务设置为SNAPSHOT隔离级别,否则将导致事务中止。
- Increasing the isolation level may result in large numbers of locks being used by the extraction utility, and may restrict database use by other users. 增加隔离级别可能导致产生大量由抽取实用程序使用的锁定,并且可能限制其他用户使用数据库。
- If a connection sets its transaction isolation level to serializable, SQL Server uses key-range locking to prevent phantoms. 如果某个连接将其事务隔离级别设置为可序列化,则SQL Server使用键范围锁来防止出现幻影。
- The percentage of those transactions using the snapshot isolation level that have encountered update conflicts within the last second. 使用快照隔离级别的、在最后一秒内遇到更新冲突的事务的百分比。
