Kbase P37680: How to set transaction isolation level for SQL server dataserver?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/22/2009 |
|
Status: Verified
GOAL:
How to set transaction isolation level for SQL server dataserver?
GOAL:
What is -Dsrv TXN_ISOLATION,n?
GOAL:
What is -Dsrv TXN_ISOLATION,1?
GOAL:
What is -Dsrv TXN_ISOLATION,2?
GOAL:
What is -Dsrv TXN_ISOLATION,4?
GOAL:
What is -Dsrv TXN_ISOLATION,8?
GOAL:
What other values can I set with -Dsrv TXN_ISOLATION?
FACT(s) (Environment):
Progress 9.1x
OpenEdge 10.x
Windows
MS SQL DataServer
FIX:
The Merant drivers provide for transaction isolation levels. In a multi-user configuration, you can isolate users from each other in your data source by setting the isolation level. In your Progress schema holder, use the -Dsrv TXN_ISOLATION,n connection parameter (where n = 1, 2, 4, or 8) to set the isolation level in ODBC.
-Dsrv TXN_ISOLATION,1 = Read uncommitted
The "-Dsrv TXN_ISOLATION,1" parameter is set to get the similar progress locking behavior
-Dsrv TXN_ISOLATION,2 = Read committed
-Dsrv TXN_ISOLATION,4 = Repeatable read
-Dsrv TXN_ISOLATION,8 = Serializable