Can somebody specify the exact difference between Isolation levels CS and RR.
consider a scenario where I am updating table through a cursor with Isolation level CS. I have updated the 5th row in cursor and now I am on 6th row. commit is not issued yet.
then, at this time, can any other application read or update the 5th row?
please refer this , i think , you will get idea about cursor stability isolation .
When the Cursor Stability isolation level is used, each row that is referenced by a cursor being used by the isolating transaction is locked as long as the cursor is positioned on that row. The lock acquired remains in effect either until the cursor is repositioned (usually by calling the FETCH statement) or until the isolating transaction terminates. Thus, when this isolation level is used, SELECT statements that are issued more than once within the same transaction may not always yield the same results. Lost updates and dirty reads cannot occur; non repeatable reads and phantoms, however, can and may be seen.
When a transaction using the Cursor Stability isolation level retrieves a row from a table via an updatable cursor, no other transaction can update or delete that row while the cursor is positioned on it. However, other transactions can add new rows to the table and perform update and/or delete operations on rows positioned on either side of the locked row, provided that the locked row itself was not accessed using an index. Furthermore, if the isolating transaction modifies any row it retrieves, no other transaction can update or delete that row until the isolating transaction is terminated, even after the cursor is no longer positioned on the modified row.