laurie-789651 (9/24/2012)
2. You could consider using
FROM Table1 SD WITH (NOLOCK) JOIN Table2 WITH (NOLOCK) etc.
as long as the table isn't being updated - this saves time as no read locks are issued.
And incorrect results are possible, not just dirty reads, duplicate or missing rows. If there are no changes being made, there's little gain from nolock, the overhead of taking locks is not that high, and it introduces the potential for incorrect results when changes are being made.
See - http://blogs.msdn.com/b/davidlean/archive/2009/04/06/sql-server-nolock-hint-other-poor-ideas.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability