READ COMMITTED SNAPSHOT Isolation Level question

  • I want to enable READ COMMITTED SNAPSHOT isolation on one of our busiest OLTP systems.

    I know this will require extra space for the tempdb files and possibly a faster disk subsystem, RAID 1 or RAID 10. I am also aware that extensive testing will be needed.

    Anything else to watch out for?

    Does anyone have any positive/negative experiences to share?

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • I'll just say that my experience was pretty positive.

    It didn't eat up much CPU or I/O for us and virtually completely cleaned up our blocking issues.

    I hoped that helped a little.

    @SQLvariant

  • Aaron Nelson (5/12/2008)


    I'll just say that my experience was pretty positive.

    It didn't eat up much CPU or I/O for us and virtually completely cleaned up our blocking issues.

    I hoped that helped a little.

    Thank you for the response.

    Did you use RAID 5 for tempdb?

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • No.

    I'm a member of Baarf. 😀

    I would never do such a thing.

    @SQLvariant

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

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