Home Forums SQL Server 2005 Administering SNAPSHOT Isolation with (NOLOCK) being used all over RE: SNAPSHOT Isolation with (NOLOCK) being used all over

  • SQL_ME_RICH (11/21/2012)


    Recently, my applications architect decided that we needed to change the level of the database Isolation from the the default READ COMMITTED to SNAPSHOT ISOLATION (basically Read Committed with Snapshot Isolation) saying that it use to be in place, and that over the course of time (and multiple server leases coming to an end and being moved to newer systems) that it had been set back to the default

    This is controlled by a SET option in the database and is therefore transfered with the database. If it's switched off then someone issued a

    ALTER DATABASE mydb SET ALLOW_SNAPSHOT_ISOLATION OFF

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉