title: Deadlock issue with SQL Server 2008 and ADO.NET
body: <p>In our applications we don't use either ADO.NET transaction or SQL Server transactions in procedures and now we are getting the below error in our website when multiple people are using. </p>
  
  <blockquote>
    <p>Transaction (Process ID 73) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction</p>
  </blockquote>
  
  <p>Is this error due to the lack of transactions? I thought the consistency will be handled by the DB itself. </p>
  
  <p>And one thing I noticed that SQLCommand.Timeout property has set to 10000. Will this be an issue for the error?</p>
  
  <p>I am trying to solve this issue ASAP. Please help.</p>
  
  <p><strong>EDIT</strong></p>
  
  <p>I saw the Isolationlevel property of ADO.NET transaction, so if I use ADO.NET transaction with proper isolationlevel property like "ReadUncommitted" during reading and "Serializable" during writing?</p>