Both Serializable and Snapshot isolation levels exclude concurrency issues such as Dirty Reads, Non-repeatable Reads and Phantoms. However the way in which they deal with such issues is quite different. In this article, Sergey Gigoyan explains the main differences between the two.
2016-01-13
3,453 reads
2014-08-14
1,901 reads
An examination into how the various transaction isolation levels affect locking (and blocking)
2014-02-13
7,693 reads
This article looks at SQL Server locking and transaction isolation levels, how to set the transaction isolation level, and how some isolation levels use locking, while others use row versioning. It also explains what type of locks data update requires.
2013-07-17
3,573 reads
Transaction Isolation levels are described in terms of which concurrency side-effects, such as dirty reads or phantom reads, are allowed.
2013-05-01
7,048 reads
2012-11-21
2,076 reads
2012-04-19
1,995 reads
2010-07-06
3,070 reads
2009-03-19
3,718 reads
2009-03-05
3,670 reads
By Steve Jones
The summary from my fourth T-SQL Tuesday hosting for #117. This time I was...
By Ed Elliott
When you run an application using spark-dotnet, to launch the application you need to...
By Cludio-Silva
Starting on dbatools version 1.0.31 we introduced better coverage for commands that make use...
Hello everyone! I'm new a DBA and I was wondering if anyone could share...
Comments posted to this topic are about the item Reading Part of a Dataframe
Comments posted to this topic are about the item The First Rule
Ask SSC