Bill, Steve, Jack and Clare,

Thanks.  I never would have guessed.   I was always under the assumption
that, under the covers, Physical and Logical file indices were more or less
just like thier SQL brethren (other than the obvious differences between a
view and an index, which still confuses me a little).

Steve - even if I had the sql product, I think storing create, alter or any
other design elements in a source file and running them from there with
runsqlstm is a good idea.  It's self documenting and all and it makes it
easier to duplicate work for identical libraries and such.

This is decidedly an 'old school' shop.  I will attempt to get the powers
that be to look more towards SQL for database design, but I won't promise

Thanks for the heads up everybody!


------original message-----------
I believe I saw a posting from Kent Milligan (IBM's DB2/400 guru)
recently on the usenet group recommending
to create indexes for performance enhancement in cases like yours.

The SQL product is not required to create indexes -
you can use RUNSQLSTM or an *QMQRY
to create indexes.

Steve Landess
Austin, Texas
(512) 423-0935

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.