title: Avoiding deadlock by using NOLOCK hint
body: <p>Once in a while I get following error in production enviornment which goes away on running the same stored procedure again.</p>
  
  <blockquote>
    <p>Transaction (Process ID 86) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction</p>
  </blockquote>
  
  <p>Someone told me that if I use NOLOCK hint in my stored procedures, it will ensure it will never be deadlocked. Is this correct? Are there any better ways of handling this error?</p>