title: Entity Framework Dead Lock Victim on Read Only Statements
body: <p>I have an OData service (WCF Data Service using Entity Framework).</p>
  
  <p>All this service does is select data.  (No writes EVER.)</p>
  
  <p>When I run my OData queries, I am occasionally getting errors like this:</p>
  
  <blockquote>
    <p>Transaction (Process ID 95) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction</p>
  </blockquote>
  
  <p>Can a select statement be a dead lock victim?  Or is Entity Framework trying to lock stuff it should not be locking?</p>
  
  <p>If it is locking where it should not be, is there a way to tell Entity Framework to NEVER lock?  (For this service it is always and for ever going to be read-only.)</p>