Isolation Levels Repeatable Read
One of my favorite SQL Server topics is isolation levels, because concurrency and consistency are crucial for any database. Which isolation level should you choose? The answer depends on your workload. However, a key goal when selecting one is to preserve consistency and increase concurrency (easier said than done).
Years ago, I steered clear of them because I didn't understand isolation levels, and the phenomena they prevented, such as phantom reads or non-repeatable reads. The best way to overcome that hurdle was to learn.
One isolation level that isn't often discussed (at least by the people I follow) is Repeatable Read. Why would you choose to use Repeatable Read, and how does it differ from Read Committed? Additionally, where does Snapshot fit in? These are just a couple of questions I investigated in my latest article on MSSQLTips.com.
SQL Server Isolation Level Comparison – Repeatable Read and Snapshot Isolation.
Have you used Repeatable Read in a real-world scenario?