June 30, 2014 at 6:29 am
Hello.
Is a good idea to use this behavior in a busy OLTP?
What is the best for that case, snapshot or read_committed_snapshot?
Thanks.
June 30, 2014 at 10:24 am
The answer to both of those is 'test it'
Read committed snapshot can be very useful, you have to test and make sure that the overhead on TempDB isn't too bad. You also need to test and ensure that you have no code which is depending on locking behaviour (eg queue-type apps)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 2 (of 2 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