title: SQL Server transactions: insert causes locks?
body: <p>I'm having the following issue:
  I'm inserting a row to table (say, 'temp') inside a transaction (default ADO.NET transaction). Until that transaction is committed, the command 'select * from temp', running from another session (SQL Server 2008 management studio), is blocked and cannot be completed. </p>
  
  <p>This seems weird to me. Shouldn't the read command return all the previous table rows (everything but the newly inserted row) and not get blocked?</p>