Posted by Dan Guzman on 05/23/07 12:26

> Is this behavior correct?

In order for the SELECT user to get the old data version in the
READ_COMMITTED isolation level, the READ_COMMITTED_SNAPSHOT database option
needs to be turned on. This was introduced in SQL 2005.


--
Hope this helps.

Dan Guzman
SQL Server MVP

"D." <d@hotmail.com> wrote in message
news:f31654$287$1@newsreader.mailgate.org...
>I have a question about the "readCommitted" transaction isolation level.
>
> I have a client that is updating a record on a table.
> I suspend the execution after the UPDATE but before the commit statement.
>
> Than another client is trying to read the same record.
>
> As transaction isolation is set to "readCommited" I expected that the
> second client will read the old version of the record (before the update).
> Instead, the second client hangs and wait until the first client do the
> commit.
> I expect this behavior if transaction isolation is set to "serializable"
>
> Is this behavior correct?
>
> Thanks,
> D.
>

[Back to original message]