| 1. | Read committed database engine default level
已提交读（数据库引擎的默认级别） |
| 2. | Both implementations meet the ansi definition of read committed isolation
两个实现都满足已提交读隔离的ansi定义。 |
| 3. | This also applies to read - committed transactions that use row versioning
这也同样适用于使用行版本控制的已提交读事务。 |
| 4. | Uncommitted read - ur
未提交读ur |
| 5. | One is a new implementation of read committed isolation , and one is a new transaction isolation level , snapshot
一个是已提交读隔离的新实现，另一个是新事务隔离级别（快照） 。 |
| 6. | Added note about row version retention for triggers and read - committed transactions using row versioning
添加了有关触发器的行版本保持期和使用行版本控制的已提交读的事务的注释。 |
| 7. | For example , reading from a read - only look up table doesn t require repeatable read , and uncommitted read is sufficient
比如，读取只读的查找表不需要可重复读级别，未提交读级别就足够了。 |
| 8. | The lowest isolation level , read uncommitted , can retrieve data that has been modified but not committed by other transactions
最低隔离级别（未提交读）可能检索到其他事务已修改但未提交的数据。 |
| 9. | The lowest isolation level , read uncommitted , may retrieve data that has been modified but not committed by other transactions
最低隔离级别（未提交读）可以检索其他事务已经修改、但未提交的数据。 |
| 10. | A new implementation of read - committed isolation level that uses row versioning to provide statement - level read consistency
已提交读隔离级别的新实现方式，它使用行版本控制来提供语句级读取一致性。 |
