SQL Server: Why we should avoid the NOLOCK table hint in DELETE/UPDATE queries

aasim abdullah

Rate me:

1.00/5 (1 vote)

12 Sep 2012CPOL1 min read

25.3K

Why we should avoid the NOLOCK table Hint in DELETE/UPDATE queries.

Revisions

Compare	Revision	Minor	Date	Status	Editor
	3 - publicly available	Yes	12-Sep-12 8:29	Available	Smitha Nishant
Updates in content.
	2	No	12-Sep-12 8:24	Available	Smitha Nishant
Updates in content.
	1	No	12-Sep-12 8:24	Available	Smitha Nishant
Updates in content. 94 changes had been made.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Written By

aasim abdullah

Team Leader CureMD

Pakistan

Aasim Abdullah is working as SQL Server DBA with CureMD (www.curemd.com) based in NY, USA. He has been working with SQL Server since 2007 (Version 2005) and has used it in many projects as a developer, administrator, database designer. Aasim's primary interest is SQL Server performance tuning. If he finds the time, he like to sketch faces with graphite pencils.

SQL Server: Why we should avoid the NOLOCK table hint in DELETE/UPDATE queries

Revisions

License

Comments and Discussions