Is it advantageous to specify NOLOCK on select statements in SQL server 7? It is my understanding that a rowlock is automatically applied, even though nothing is modified. Any thoughts?
When this option is in effect, it is possible to read an uncommitted transaction or a set of pages that are rolled back in the middle of a read. Dirty reads are possible. Only applies to the SELECT statement.<BR>I recommend you leave it alone!