Row Versioning

Article

In any database, mismanagement of transactions often leads to contention and performance problems in systems that have many users. As the number of users that access the data increases, it becomes important to have applications that use transactions efficiently. This guide describes the locking and row versioning mechanisms the SQL Server Database Engine uses to ensure the physical integrity of each transaction and provides information on how applications can control transactions efficiently.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2022-10-05

SQL Server 2005 Row Versioning-Based Transaction Isolation

by Additional Articles

TechNet Blogs

Row Versioning

Article

Microsoft SQL Server 2005 provides nonlocking, nonblocking read consistency to your users through snapshot isolation and read committed isolation using row versioning. Find out when you can use these features to improve performance and reduce latency in your applications.

2009-05-01

2,535 reads

Read the latest Blogs

Visit the forum

Question of the Day

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

Row Versioning

Transaction locking and row versioning guide

SQL Server 2005 Row Versioning-Based Transaction Isolation

Blogs

Did You Really Name That Default?

Monday Monitor Tips: A New Analysis Page

Case Studies: Real-World Success Stories of FinOps Implementation

Forums

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions

Identity Defaults

Question of the Day

Identity Defaults