Avoid Locking Conflicts

By Bill Graziano on 18 September 2000 | 0 Comments | 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.
Follow the link to Avoid Locking Conflicts...

Discuss this article: 0 Comments so far. Print this Article.

If you like this article you can sign up for our weekly newsletter. There's an opt-out link at the bottom of each newsletter so it's easy to unsubscribe at any time.

Email Address:

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

Foreign Key Table index - drop or disable (3 Replies)

Remove Primary Key from ID column (6 Replies)

Issue with db design (3 Replies)

Re-establishing a mirror (3 Replies)

Need help comparing values in the same field (2 Replies)

Problem with Date fields (11 Replies)

Help please! (1 Reply)

Return error of a timeouted server (7 Replies)

Subscribe to SQLTeam.com

Weekly SQL Server newsletter with articles, forum posts, and blog posts via email. Subscribers receive our white paper with performance tips for developers.

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -