![]() | |
#1
| |||
| |||
|
|
Please read the following posts by Craig Freedman, member of the SQL Server query execution team: http://blogs.msdn.com/craigfr/archiv...ion-level.aspx http://blogs.msdn.com/craigfr/archiv...ion-level.aspx http://blogs.msdn.com/craigfr/archiv...ion-level.aspx Is the behaviour described in these posts the *correct* behaviour, as defined by ANSI SQL standards, considering the Read Committed and Repetable Read isolation levels, respectively ? Do other DBMS-s behave the same way ? I am aware that the behaviour would be different if we use snapshot isolation, but I'm interested how things *should* work without snapshot isolation. I'd like some responses from people who know really well the ANSI SQL standard and the isolation levels defined in it. |
#2
| |||
| |||
|
|
Razvan Socol wrote: Please read the following posts by Craig Freedman, member of the SQL Server query execution team: http://blogs.msdn.com/craigfr/archiv...ion-level.aspx http://blogs.msdn.com/craigfr/archiv...ion-level.aspx http://blogs.msdn.com/craigfr/archiv...ion-level.aspx Is the behaviour described in these posts the *correct* behaviour, as defined by ANSI SQL standards, considering the Read Committed and Repetable Read isolation levels, respectively ? Do other DBMS-s behave the same way ? I am aware that the behaviour would be different if we use snapshot isolation, but I'm interested how things *should* work without snapshot isolation. I'd like some responses from people who know really well the ANSI SQL standard and the isolation levels defined in it. |
|
Thinking you might get a better response from comp.databases, I am cross-posting your question there. |
![]() |
| Thread Tools | |
| Display Modes | |
| |