Kbase P162017: Is it possible to force the Transaction Isolation Level by the SQL Engine
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/03/2010 |
|
Status: Unverified
GOAL:
Is it possible to force the Transaction Isolation Level by the SQL Engine
GOAL:
Is it possibility to force SQL engine to use only the READ_UNCOMMITTED Transaction Isolation Level
FACT(s) (Environment):
Connecting with an ODBC client application which sets the Transaction Isolation Level to READ_COMMITTED
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
No. The OpenEdge SQL engine does not have the ability to force a particular type of client application (ODBC) to have a predefined Transaction Isolation Level (read uncommitted). Our SQL server does not know that a particular client application is using ODBC and the server has no configuration option, or a command, to force a client connection (other than itself) to have a given Transaction Isolation Level.
In OpenEdge SQL, only the SQL client controls the Transaction Isolation Level.
If you could stop the ODBC application setting a Transaction Isolation Level then the default Transaction Isolation Level in the ODBC DSN could be used to set up Read Uncommitted as the Transaction Isolation Level.
For the case there is no way to tell your ODBC application to stop the setting a Transaction Isolation Level and your business case would justify your requirement to have such a new feature implemented than you could submit an enhancement request at:
http://www.progress.com/cgi-bin/ers.cgi/login.htm