Hi- I am just practicing. I might have posted a confusing question before.
I want to see how selects behave differently with being in different isolation contexts rather than just running the default snapshot like in isql with nothing else going on (no other transactions). This is an example of a situation where a select might behave a little differently when dealing with different isolation levels. The first select locks the entire table, and the second select tries to read the employee table, and it can't even read the record with emp_no 144 until the first change is committed. I will continue to practice with two flameRobins open. Here are two different transactions and queries. 1. set transaction read only table stability wait; update employee set last_name = 'k135' where emp_no = 144; 2. set transaction read only read committed record_version no wait; select * from employee; I hope everyone is having a cool weekend. thanks, 3rdshiftcoder
