Locking

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

Blogs

Understanding Zonal Redundancy in Azure SQL MI

By

Do you know what happens when you enable zonal redundancy for your SQL managed...

SQL Server Database Compatibility Levels

By

Why You Shouldn’t Overlook This Quiet but Critical SQL Server Setting   If you’ve...

The PASS Summit on Tour in the Netherlands

By

The PASS Summit goes on tour this year, with the final date the first...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

Top Quality Boomerang Booth Rental for Corporate Events

By Sam1Parker

Make your corporate events more engaging with a fun twist. Our booths capture energetic...

How do I make this one row per id

By ajillity81

I've written this code, but it is showing right now as 2 rows per...

Visit the forum

Question of the Day

The Updated Columns List

I have this table in SQL Server 2022:

CREATE TABLE CustomerLarge
  (CustomerID               INT NOT NULL IDENTITY(1, 1) CONSTRAINT CustomerLargePK PRIMARY KEY CLUSTERED
 , CustomerName             VARCHAR(20)
 , CustomerContactFirstName VARCHAR(40)
 , CustomerContactLastName  VARCHAR(40)
 , Address                  VARCHAR(20)
 , Address2                 VARCHAR(20)
 , City                     VARCHAR(20)
 , CountryCode              CHAR(3)
 , Postal                   VARCHAR(20)
)
GO
If I check the columns_updated() function return in a trigger, what is the data returned?

See possible answers