Post reply

snapshot isolation understanding.

  • May 4, 2009 at 10:40 am

    #133771

    I read SQL Server 2005 provides nonlocking, nonblocking read consistency to users through a new isolation called snapshot isolation with row versioning.

    but what i could not understand after reading a blog is - To use transaction-level snapshot isolation, you will have to change the application to use it. I am confused as to what needs to be change at the application? cant i enable snapshot isolation at the database level and all will be taken care? EG:

    ALTER DATABASE Prod SET read_committed_snapshot ON;

    also whats the different between statement-level consistency and transaction-level consistency?

    appreciated any input.

    Thanks,

  • May 4, 2009 at 8:32 pm

    #988514

    Drop the following into the URL field of BOL for how to implement it. It has nothing to do with the app...

    ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/035b3297-6f89-4043-9ba0-76108781b827.htm

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

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

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