RE: Single record access really required (was RE: Views and

A couple of questions on this argument:

What does IAAI stand for and how are they involved with performance
issues?

Is DB2/400 like VM & MVS DB2, such that when you create tables inside
of DB2 you can't read the data except with SQL and the security inside
of theDB2 engine?  If that is true, then I prefer SQL for programming
applications, at least from the security aspect.   And, if the DB2/400
optimizer is anything like the VM/MVS DB2 optimizer, I'd say that you'll
get better performance with DB2 over the keyed-sequence record-at-a-time
access of the native 400 I/O but usually only IF you have large numbers
of records.  The reason for this is because the DB2 Optimizer makes
decisions on how to best get your data, and those decisions may change
day-to-day, whereas the keyed sequence approach goes through keys and
follows much the same path regardless of how circumstances have changed
and may not be the best performer.   It is important to make
apples-to-apples comparisons as far as the data and the application
architecture.   I hope, if the IAAI is into performance comparisons the
comparison test are set up in a fair manner using the coding access
strategy best for each access method and not forcing a key-sequence
approach using SQL or vice versa. 

FWIW,

Dave Odom