Kbase P117575: Performance of ODBC DataServer vs. Progress/400 with DB2/400 explained
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
04/09/2008 |
|
Status: Verified
GOAL:
Performance of ODBC DataServer vs. Progress/400 with DB2/400 explained
FACT(s) (Environment):
OpenEdge 10.x
ODBC DataServer
Progress/400 DataServer
Progress 9.1C
FIX:
As a general rule: OpenEdge and Native AS/400 data access share much in common. They are both use a transactional approach to data access that is based on optimizing random record access. UDB/400 and the ODBC DataServer are SQL based which means data retrieval is optimized for set based access.
The Progress and native AS/400 approach allows for optimized performance with FIND statements. SQL's set-based approach optimizes data access for queries and FOR EACH's. Because of these differences, one can expect that random access like FINDs may have better relative performance with OpenEdge and Native AS/400 data access and Queries/FOR EACHs may have better relative performance in SQL-based database environments such as the ODBC, MS SQL Server and Oracle DataServers.
It is suggested to replace FINDs with FOR EACHs and queries, this would "generally speaking" improve ODBC performance. FIND FIRSTs could be quickly optimized with FOR FIRST's.