| 1. | Read committed database engine default level 已提交读(数据库引擎的默认级别) |
| 2. | Read committed using row versioning 使用行版本控制的read committed |
| 3. | Read committed read uncommitted 读取提交的结果 |
| 4. | Both implementations meet the ansi definition of read committed isolation 两个实现都满足已提交读隔离的ansi定义。 |
| 5. | Off transactions specifying the read committed isolation level use locking 指定read _ committed隔离级别的事务使用锁定。 |
| 6. | This leaves you a choice between read committed and repeatable read 剩下的也就是在“授权读取”和“可重复读取”之间选择了。 |
| 7. | Transactions specifying the read committed isolation level use row versioning instead of locking 指定read _ committed隔离级别的事务使用行版本控制而不是锁定。 |
| 8. | When off is specified , transactions that specify the read committed isolation level use locking 当指定为off时,指定read _ committed隔离级别的事务将使用锁定。 |
| 9. | Specifies that read operations comply with the rules for the read committed isolation level by using locking 指定读操作使用锁定来遵循有关read committed隔离级别的规则。 |
| 10. | One is a new implementation of read committed isolation , and one is a new transaction isolation level , snapshot 一个是已提交读隔离的新实现,另一个是新事务隔离级别(快照) 。 |