>>-SET TRANSACTION---------------------------------------------->
 
   .-,------------------------------------------------.
   V    (1)                                           |
>----+--------+-READ WRITE-+------------------------+-+--------><
     |        '-READ ONLY--'                        |
     |  (1)                                         |
     '--------ISOLATION LEVEL--+-READ COMMITTED---+-'
                               +-REPEATABLE READ--+
                               +-SERIALIZABLE-----+
                               '-READ UNCOMMITTED-'
 

1. Use path no more than once

SET TRANSACTION is valid only in databases with transaction logging. You can issue a this statement from a client computer only after a database is opened. The database isolation level affects concurrency among processes that attempt to access the same rows simultaneously from the database. The database server uses shared locks to support different levels of isolation among processes that are attempting to read data, as the following list shows:

• Read Uncommitted
• Read Committed
• (ANSI) Repeatable Read
• Serializable

The update or delete process always acquires an exclusive lock on the row that is being modified. The level of isolation does not interfere with such rows, but the access mode does affect whether you can update or delete rows.

If another process attempts to update or delete rows that you are reading with an isolation level of Serializable or (ANSI) Repeatable Read, that process will be denied access to those rows.