Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • I tried Repeatable Read in SQL Server 2008 with "set isolation level repeatable read". Created two sql query windows. But did not work. Why? Commented Aug 17, 2013 at 1:57
  • 1
    Why would the second session1 still read out Aaron? Isn't session2's transaction finished and commited? I know this old, but maybe someone can shed some light. Commented May 20, 2015 at 12:27
  • 23
    I think the Repeatable Read will block the second session until the first session committed. So the example is wrong. Commented Jul 22, 2016 at 9:22
  • 6
    In case of Repeatable Read, when session 1 reads the row, it puts a shared lock, which would not allow any Exclusive lock (to session 2) for update, hence the data cannot be updated. Commented Mar 20, 2017 at 16:58
  • 3
    I think SQL server and MySQL behave differently when it comes to update of shared rows between two transactions Commented Jun 28, 2019 at 6:46