| 1. | This leaves you a choice between read committed and repeatable read
剩下的也就是在“授权读取”和“可重复读取”之间选择了。 |
| 2. | Repeatable read - rr
可重复读rr |
| 3. | This is an important issue , but using repeatable read isn ' t the only way to resolve it
这是一个非常重要的问题，但是使用可重复读取并不是解决问题的唯一途径。 |
| 4. | For example , reading from a read - only look up table doesn t require repeatable read , and uncommitted read is sufficient
比如，读取只读的查找表不需要可重复读级别，未提交读级别就足够了。 |
| 5. | If the transaction isolation mode is repeatable read , then the optimizer would base its choice purely on the estimated costs
如果事务隔离模式是可重复读（ repeatable read ） ，那么优化器会将其选择完全基于估算成本。 |
| 6. | If the value is set to 1 , then the optimizer behaves as it does for value 0 if the transaction isolation mode is not repeatable read
如果将其值设置为1 ，那么当事务隔离模式不是可重复读（ repeatable read ）时，优化器的行为就与值为0时一样。 |
| 7. | In a repeatable read or serializable transaction , the transaction reads data , acquiring a shared lock on the resource page or row , and then modifies the data , which requires lock conversion to an exclusive lock
在可重复读或可序列化事务中，此事务读取数据[获取资源（页或行）的共享锁（ s锁） ] ，然后修改数据[此操作要求锁转换为排他锁（ x锁） ] 。 |
| 8. | Shared locks on a resource are released as soon as the read operation completes , unless the transaction isolation level is set to repeatable read or higher , or a locking hint is used to retain the shared locks for the duration of the transaction
读取操作一完成，就立即释放资源上的共享锁（ s锁） ，除非将事务隔离级别设置为可重复读或更高级别，或者在事务持续时间内用锁定提示保留共享锁（ s锁） 。 |
| 9. | Transactions must be run at an isolation level of at least repeatable read to prevent lost updates that can occur when two transactions each retrieve the same row , and then later update the row based on the originally retrieved values
当两个事务中的每个事务都要检索相同的行，然后又根据最初的检索值更新行时，可能发生更新丢失。此时，事务必须至少以的可重复读的隔离级别运行，以防止更新丢失。 |
| 10. | Setting the transaction isolation level to repeatable read means that both the independent select statement in example 1 and the select statement contained in the declare cursor of example 2 generate share locks on each row they read , and the share locks are held until the transaction is committed or rolled back
将事务隔离级别设置为可重复读意味着：示例1中的独立select语句和示例2中的declare cursor包含的select语句在所读取的每一行上都生成共享锁，并且这些共享锁一直保持到事务提交或回滚。 |
