Post reply

READ_COMMITTED_SNAPSHOT database option

  • April 30, 2008 at 12:58 pm

    #181878

    So I've read a little bit about the DB option READ_COMMITTED_SNAPSHOT and found reasons I should try it out, but nothing about negative consequences if I do impliment it. Is there any reason that I wouldn't want this option on (performance or otherwise)?

    Thanks

  • April 30, 2008 at 1:12 pm

    #809277

    You do take a performance hit. Every transaction needs to maintain the previous version of records impacted while the transaction is running. The impact (in my experience using it) is pretty low, but it is there.

    The big impact is in application design. Management of locked resources is different and you may want to handle some things differently. Overall, I have found using it to be fairly positive.

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

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