GilaMonster (4/12/2013)
There is, but to be honest you shouldn't be using nolock everywhere. It's not a go-faster switch, it is not a performance tuning technique, it is not necessary to make queries fast (if you have problems with blocking, you need to tune the queries, not hide the symptoms)Nolock allows incorrect data, not just dirty reads, duplicate rows, missed rows and other similar fun. I suggest you pass this onto your colleagues.
See - http://blogs.msdn.com/b/davidlean/archive/2009/04/06/sql-server-nolock-hint-other-poor-ideas.aspx
I hope that's not financial data that you're querying there. Do all the users know and accept that the data they see could be very wrong?
Thanks for answer me
In my company, we are querying financial data, because we support Collection Agencies. I don't know if my co-works know about nolock issues as well.
However I must to prove the company managers (Project Manager) that nolock is worst solution.
Could you mind to give me some examples?