this is last time on this topic i want to clarify myself with the NOLOCK using in my script.
when i use some told me dirty read and some times it get essential to use as it locked the table and other who are using not able to run simple select as some of them running a typical query with lots of time cosumption.
and how use of it get differ with platform. i am specially interested with production envirionmnt.... question needs to be cleared from you respected expertise.......also to know disadvantage and all point to keep in mind for Read_Committed_snapshot isolation level
Using (NOLOCK) is not a practice that I would consider in most situations, mainly for the reason you already mentioned (dirty reads).
If you are experiencing locking and blocking, I would first think that there are other issues on your system that need looking at that are causing you to look at NOLOCK and row versioning solutions.
Quite often, poor query design and inadequate indexing cause systems to experience the sort of issues you are hinting at.
Be that as it may, to answer on the Read Commited snapshot isolation level, take a look at the [Row Verisioning information on MSDN]: http://msdn.microsoft.com/en-us/library/ms177404.aspx
answered Nov 09 '11 at 11:47 PM