[dba-SQLServer] NoLocks

if it's not likely to change then you should receive a performance boost
simply by going to nolocks, because the engine does not engage a lock for
the rows or pages it is reading.  The only real caveat is when you are
worried about dirty reads, that is data that could be in the processes of
changing.

-Francisco
http://sqlthis.blogspot.com | Tsql and More...


On Tue, Feb 10, 2009 at 3:38 PM, David Emerson <newsgrps at dalyn.co.nz> wrote:

> I have a sproc that runs slow due to the large number of sub
> processes it goes through.
>
> I was wondering what potential problems I could have if I used
> NoLocks in the select statements.  The data that is being processed
> is not likely to change during running the sproc (famous last words).
>
> Any comments?
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>