Posted by Erland Sommarskog on 06/23/07 09:10

Oscar Santiesteban (o_santiesteban@bellsouth.net) writes:
> Try using
> select * from table (NOLOCK)
> where xxxx = xxxx
> This will not lock the database as it reads.

This may on the other hand lead to that the query returns incorrect
results, which may even more seroius. There are situations where NOLOCK
is called for, but you need to understand the implications. If you
don't - don't try it.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Foreign Key
• Prev in forum: Re: BULK INSERT ignores UNIQUE index with IGNORE_DUP_KEY set?
• Thread view: Re: Deadlock transaction

[Reply to this message]