April 30, 2008 at 12:58 pm
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
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
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy