transaction isolation

SQLServerCentral Article

The Record That Never Existed (as a committed row)

  • Article

Introduction According to the official documentation, the READ COMMITTED isolation level “specifies that statements cannot read data that has been modified but not committed by other transactions”. So, one could think that a record returned under this isolation level existed in the committed state at the time of reading. In this article, I am going […]

(1)

You rated this post out of 5. Change rating

2021-10-01

2,169 reads

Blogs

Audit – Security Compliance Frameworks (Part 1)

By

This blog series on Audit/Compliance/Security, this is first blog where we would discuss about...

Restore SQL Server Database to an OrbStack Container

By

In the previous post, we've built a SQL Server 2025 sandbox in an OrbStack...

Day of Data Baton Rouge Slides and Code

By

Thanks to everyone for attending my talk today at Day of data Baton Rouge...

Read the latest Blogs

Forums

Can You Really Downgrade from Enterprise to Standard and Save Thousands? Here's What Happened

By Pablo Echeverria

Comments posted to this topic are about the item Can You Really Downgrade from...

What is CPU Usage?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What is CPU Usage?

Limiting Checkpoints

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Limiting Checkpoints

Visit the forum

Question of the Day

Limiting Checkpoints

If I use the -k parameter with a number after it, what does this change in SQL Server?

See possible answers