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

Lost updates may occur even if reads and writes are in separate transactions, like when users read data into Web pages, then update. In such cases no isolation level can protect you, especially when connections are reused from a connection pool. We should use other approaches, such as rowversion. Here is my canned answer.