Wonder ( XXXX@XXXXX.COM ) writes:
If there is only one user, there is no reason to use NOLOCK is there?
NOLOCK is a gamble, and if you don't understand the exact implications
of NOLOCK, you should ont use it. Even if there is a single user on the
system, a reindexing or defragmentation job that runs simultaneously
could cause problems.
Erland Sommarskog, SQL Server MVP, XXXX@XXXXX.COM
Books Online for SQL Server 2005 at
Books Online for SQL Server 2000 at