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

Friday Flyway Tips–Comparison Options

By

Recently a customer asked how they could get index changes to be captured in...

A New Word: Guiltwrights

By

giltwrights  – n. the imaginary committee of elders that keeps a running log of...

Becoming Kristyna Ferris <3

By

Hey folks, fun personal post today. A few weeks ago, I got married! My...

Read the latest Blogs

Forums

PostgreSQL authenticated against Microsoft Active Directory

By SSRSNoob

Can I authenticate with Active Directory and get into PostgreSQL? Version: PostgreSQL 16.1 on...

Compare all tables row counts for 2 server instances?

By lan2022nguyen

USE [DBName] SELECT QUOTENAME(SCHEMA_NAME(sOBJ.schema_id)) + '.' + QUOTENAME(sOBJ.name) AS [TableName] , SUM(sPTN.Rows) AS [RowCount]...

Backing Up Master

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Backing Up Master

Visit the forum

Ask SSC Logo Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers