Sql server lock table while updating Chatbotsex
The owning session ID can change for distributed and bound transactions.
The table is being locked because all rows have to be looked at.
The second batch, running in the default transaction isolation level of will return only after a commit or rollback has been completed in the first session.
From here you can look at your query plans and the associated lock levels, but better yet, you can read all about locks in SQL Server here.
Edit 3: I just realized I'm not considering the effect of a background checkpoint which writes an as of yet uncommitted transaction to disk, so yes, my explanation was misleading.
In the second query, the first batch can ( and in this case, will ) return uncommitted data.