da1e27dd   
   From: esquel@sommarskog.se   
      
   codefragment@googlemail.com (codefragment@googlemail.com) writes:   
   > -- NB nothing is really changing here   
   > update table1 set somecolumn1=1, somecolumn2=1   
      
   And that is the key to it all. Since nothing changes, there is no need   
   to take out any locks.   
      
   In SQL 2000, I see exclusive key lock on the index, this does not appear   
   in SQL 2008. So this is why the query "SELECT somecolumn1 FROM table1"   
   is not blocked.   
      
   What is a little puzzling is that I do see four RID locks on the table   
   as well, which would indicate that a table scan would block, but not so.   
   I don't really know what is going on here.   
      
   Whatever, I hope this is not something that is important the application   
   you work with. If it is, I suspect that there are better solutions   
   altogther.   
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
   SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)