读取已提交的快照VS快照隔离级别 [英] Read committed Snapshot VS Snapshot Isolation Level

问题描述

请问有人可以帮助我理解何时在SQL Server中通过READ COMMITTED SNAPSHOT使用SNAPSHOT隔离级别吗?

Could some one please help me understand when to use SNAPSHOT isolation level over READ COMMITTED SNAPSHOT in SQL Server?

我了解在大多数情况下，READ COMMITTED SNAPSHOT可以工作，但不确定何时进行SNAPSHOT隔离.

I understand that in most cases READ COMMITTED SNAPSHOT works, but not sure when go for SNAPSHOT isolation.

谢谢

推荐答案

READ COMMITTED SNAPSHOT进行乐观读取和悲观写入.相反，SNAPSHOT进行乐观读取和乐观写入.

READ COMMITTED SNAPSHOT does optimistic reads and pessimistic writes. In contrast, SNAPSHOT does optimistic reads and optimistic writes.

Microsoft建议大多数需要行版本控制的应用程序使用READ COMMITTED SNAPSHOT.

Microsoft recommends READ COMMITTED SNAPSHOT for most apps that need row versioning.

阅读这篇出色的Microsoft文章:选择基于行版本控制的隔离级别.它说明了两个隔离级别的好处和成本.

Read this excellent Microsoft article: Choosing Row Versioning-based Isolation Levels. It explains the benefits and costs of both isolation levels.

这是更全面的一个: http://msdn.microsoft.com/en-us/library/ms345124(SQL.90).aspx

And here's a more thorough one: http://msdn.microsoft.com/en-us/library/ms345124(SQL.90).aspx

这篇关于读取已提交的快照VS快照隔离级别的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！