Row Versioning

Technical Article

Transaction locking and row versioning guide

  • 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

Technical Article

SQL Server 2005 Row Versioning-Based Transaction Isolation

  • 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.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2009-05-01

2,535 reads

Blogs

T-SQLTuesday 204: Are blogs still relevant?

By

This month’s blogging party is hosted by Jeff Ianucci – his challenge is to...

Are Blogs Still Relevant? I Think They Still Are.

By

As for me, I'll keep writing whenever time permits. I don't expect every post...

Reading Blogs: T-SQL Tuesday #204

By

This is an interesting invitation this month. Jeff Ianucci is a new host, and...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

Switching Schemas I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Switching Schemas I

Enforcing Unique Customer Emails When Duplicates Already Exist

By Imran2629

Comments posted to this topic are about the item Enforcing Unique Customer Emails When...

Visit the forum

Question of the Day

Switching Schemas I

I run this query:

SELECT 
 s.name AS schemaname
 , o.name AS objectname
 FROM sys.objects o
 INNER JOIN sys.schemas s ON s.schema_id = o.schema_id
 WHERE o.name = 'Beer'
I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beer
What happens?

See possible answers