2025-12-12
289 reads
2025-12-12
289 reads
This article explores how enabling READ_COMMITTED_SNAPSHOT on your SQL Server database might ease excessive blocking.
2024-08-19
2023-09-04
433 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
43,350 reads
2020-02-18
1,137 reads
2019-10-28
7,316 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,971 reads
An examination into how the various transaction isolation levels affect locking (and blocking)
2014-02-13
9,078 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 SQLPals
How to Clear the SSMS Cache (SSMS 21 and Later) Updated...
By Arun Sirpal
“What exactly did it do on my server?” is the first question a DBA...
By James Serra
Microsoft shared a broad set of Fabric, Power BI, and SQL updates at FabCon...
Comments posted to this topic are about the item Let's Talk Certifications
Comments posted to this topic are about the item The Hidden Security Risks of...
Comments posted to this topic are about the item The Empty Aggregate
I have this table in a SQL Server 2025 database:
CREATE TABLE [dbo].[CustomerOrder] ( [OrderID] [int] NULL, [CustomerID] [int] NULL, [total] [money] NULL ) ON [PRIMARY] GOWhat is returned from this code? (answers are for the sum and then the count)
SELECT SUM(total) AS sum,
COUNT(total) AS count
FROM dbo.CustomerOrder;
See possible answers