Post reply

Repeatble Read Isolation level

  • February 22, 2017 at 9:21 am

    #335105

    Hi,

    I am a little confused about the repeatable read isolation level.
    As per the Microsoft 
    "Specifies that statements cannot read data that has been modified but not yet committed by other transactions and that no other transactions can modify data that has been read by the current transaction until the current transaction completes."

    Here for the first statement (Specifies that statements cannot read data that has been modified but not yet committed by other transactions )
    I am not able to find any example for this scenario.
    Can anyone help in finding the example of this statement.

    I am able to get the examples of second statement where second transaction cannot update the data read by the current transaction but first statment is not clear and I need example for the same.

    Thanks in advance

  • February 22, 2017 at 9:58 am

    #1929777

    The first statement is the same as the behaviour in read committed. Session one starts a transaction, updates a row. Session 2, in read committed or repeatable read cannot read that updated row until session 1 commits or rolls the transaction back.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • February 22, 2017 at 9:31 pm

    #1929886

    Thank for your reply.

    I was in the same confusion. You removed my confusion

    Thanks
    Amit

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply