Page History
...
| Note |
|---|
| Note: Careful consideration must be given when specifying this value as it affects all ODBC database connections for the executing application. This is an issue between you, the designer of the application, and your chosen database management system. |
Value | Transaction Isolation Level | Meaning |
|---|---|---|
0 | SQL_TXN_READ_COMMITTED | Refer to Value 2 unless the default for the database is higher. |
1 | SQL_TXN_READ_UNCOMMITTED | Dirty reads, non-repeatable reads and phantoms are possible. This is the default for SQL Anywhere. |
2 | SQL_TXN_READ_COMMITTED | Dirty reads are not possible. Non-repeatable reads and phantoms are possible. |
This is the default for Oracle and SQL Server. | ||
3 | SQL_TXN_REPEATABLE_READ | Dirty reads and non-repeatable reads are not possible. Phantoms are possible. |
4 | SQL_TXN_SERIALIZABLE | Transactions are serializable. Dirty reads, non-repeatable reads and phantoms are not possible. |
6 | SQL Server only: SQL_TXN_SS_SNAPSHOT | Refer to LANSA and SQL Server - Configuration Options in the Tips and Techniques on the LANSA web site. |
Platform Specific Notes
IBM i:
...