Kbase P120862: Using DataServer MAX_ROWS parameter causes ODBC DataServer performance degradation
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/1/2006 |
|
Status: Unverified
FACT(s) (Environment):
IBM AS/400 (RISC)
OpenEdge 10.1A
ODBC DataServer
SYMPTOM(s):
Using DataServer MAX_ROWS parameter causes ODBC DataServer performance degradation
OpenEdge 10.1A ODBC Wire Protocol driver for DB2 v.5.10.00.24
The issue occurs only when querying tables that contain PROGRESS_RECID field for rowid support.
-Dsrv MAX_ROWS parameter causes generation of inexplicable SQL statements, which degrade response times
IBM SQL Optimizer doesn't find appropriate index for additional queries even though it exists
When running the same query without MAX_ROWS parameter a proper query is being generated and an existing index is used.
CAUSE:
This is a known issue being investigated by Development
FIX:
The only workaround at the moment is to remove -Dsrv MAX_ROWS,nnnn parameter from the connection string