Home | Weblogs | Forums

Site Sponsored By: SQLDSC - SQL Server Desired State Configuration

Avoid Locking Conflicts

By Bill Graziano on 18 September 2000 | Tags: Locking

SQL Server uses locking to protect multiple transactions from trampling one another. This is a critical feature for any multiuser database system. It's also a necessary one if you want to provide concurrency between multiple transactions. High concurrency means many users can experience good response time with little conflict from other users.

Link: Avoid Locking Conflicts

Related Articles

Application Locks (or Mutexes) in SQL Server 2005 (7 January 2008)

Introduction to Locking in SQL Server (12 December 2007)

SQL Server Lock Contention Tamed: The Joys Of NOLOCK and ROWLOCK (11 October 2000)

Row Locking (13 August 2000)

Other Recent Forum Posts

Query performance Call Center data (20h)

Looking for on Premises tool to read data from SQL logs and populate data warehouse (1d)

Possible SQL 2014 to 2016 Issue - Some Application Functions Slow/Failing (1d)

Working with multiple WHERE statements (1d)

Create a new field value that shows a difference in value from 2 fields (3d)

Hierarchy wise Sales Targets (3d)

Get the MaxDate in results (5d)

Switch Statement within a SSRS SQL Expression (6d)

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources