Minimum transaction isolation level to avoid “Lost Updates”

Question

With SQL Server\'s transaction isolation levels, you can avoid certain unwanted concurrency issues, like dirty reads and so forth.

The one I\'m interested in right n

Answer 1

My experience is that with Read Uncommitted you no longer get 'lost updates', you can however still get 'lost rollbacks'. The SQL trainer was probably referring to that concurrency issue, so the answer you're likely looking for is Repeatable Read.

That said, I would be very interested if anyone has experience that goes against this.