look at the execution plan for session 1, it does a clustered Index scan. The scan hits the locked key for the new row in session 2 and is blocked...