2025-12-12
235 reads
2025-12-12
235 reads
This article explores how enabling READ_COMMITTED_SNAPSHOT on your SQL Server database might ease excessive blocking.
2024-08-19
2023-09-04
400 reads
Learn a bit about concurrency problems in SQL Server, the issues they create, and the different isolation levels that help you solve them.
2020-05-12
42,592 reads
2020-02-18
1,110 reads
2019-10-28
7,226 reads
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,942 reads
An examination into how the various transaction isolation levels affect locking (and blocking)
2014-02-13
9,026 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
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
By Steve Jones
We have multiple teams (8) working on Redgate Monitor. Some work on the Standard...
By HeyMo0sh
Learning any kind of theory is easy, but adapting FinOps and watching it rescue...
Comments posted to this topic are about the item The day-to-day pressures of a...
Comments posted to this topic are about the item The Problem Isn't Always Your...
Comments posted to this topic are about the item Identity Defaults
What happens when I run this code?
CREATE TABLE dbo.IdentityTest
(
id int IDENTITY(10) PRIMARY KEY,
somevalue VARCHAR(20)
)
GO
See possible answers