This is a very old thread - if using SQL2005 or later I recommend that you use READ_COMMITTED_SNAPSHOT - it provides the benefits of NOLOCK that developers are normally looking for (READs don't block WRITES) and none of the disastrous side effects of NOLOCK, plus you don't have to modify your code (well, you do need to remove NOLOCK if you have been using that because it still has the same disastrous side effects ...)