Choosing Row Versioning-based Isolation Levels
For most applications,read committed isolation using row versioning
is recommended over snapshot isolation for the following reasons:
It consumes less tempdb space than snapshot isolation.
Snapshot isolation is vulnerable to update conflicts that are not applicable to read committed isolation using row versioning. When a
transaction running under snapshot isolation reads data that is then
modified by another transaction,an update by the snapshot transaction
to the same data causes an update conflict and the transaction
terminates and rolls back. This is not an issue with read committed
isolation using row versioning.
我对这些主题不太了解,但我似乎无法理解上面链接中的两个要点.
>为什么这些模式的tempdb空间不同？是否存储比其他版本更精细的版本控制？
>为什么快照隔离更容易受到更新冲突的影响？
