Use NOLOCK hint to avoid block - this is what I have often heard/see in many forums I participate, during local user group events and meeting. I have always advised that its not that good idea to use hints, as it may cause data corruption and blocking. And, anyways, there are many things that you can do to avoid blocking, like:
- use sp for everything (almost)
- try to avoid using cursor
- transaction shouldn't be too big etc
- and, use READPAST hint , I will still say, use this only when you don't have choice
But these all comes from the experience from the field and haven't anything concrete to quote as reference point until last night, I was googling something and this blog article from Dave, on MSDN Blog showed up. Now, I can quote SQL Server NOLOCK Hint and Other poor ideas as reference to my peers,and friends at local user group, and I am referencing it here for you to read and make a note.
I hope this helps.
-- Hemantgiri S. Goswami (http://www.sql-server-citation.com/)
I hope this helps.
-- Hemantgiri S. Goswami (http://www.sql-server-citation.com/)
