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

A New Word: the Wends

By

the wends– n. the frustration that you’re not enjoying an experience as much as...

7 Best Online Advanced SQL Training Courses to Learn in 2024 and Beyond

By

The world runs on data, and SQL is the key to unlocking its secrets....

Manually Updating Redgate Monitor/SQL Monitor Patch Info

By

This post looks at updating the patch information for SQL Monitor/Redgate Monitor without using...

Read the latest Blogs

Forums

Pipeline Failure Route not working

By rjdineen

Hi there, I have a couple of Stored Proc tasks, that fire off after...

extracting cloud based netsuite data from the cloud in ssis

By stan

Hi we are going to need to extract netsuite data from the cloud.  This...

SQL Server Always

By ptotham

  We have a Windows Server 2022 Failover Cluster with 3 nodes SQL Server...

Visit the forum

Question of the Day

Default Objects in Clones

On SQL Server 2022, I do this:

USE model
GO
CREATE TABLE dbo.DBALog
(logdate DATETIME2(3), logmsg VARCHAR(2000))
GO
I then create a new database:
CREATE DATABASE INVENTORY
GO
I install a new database application in here with multiple tables, views, etc. I do not run any queries. I then decide to run this code:
DBCC CLONEDATABASE(INVENTORY, Inventory_clone);
GO
What happens?

See possible answers