× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



however I've been approached with the thought that Option2 will index
over an index which would be less preferable to indexing over a
non-keyed
Physical. Is this a valid concern?

Not a valid concern. An indexed physical isn't the same as, say, a
"clustered index" on something like SQLServer. Even if you key the
physical, the data is still loaded into the data space in arrival
sequence, and all other logicals will point directly at the physical
rows, there's not a level of indirection there. For all practical
purposes the keyed physical works just like the physical + logical
setup... except there is only one *file object, not two. IIRC, if you
define the keyed physical on an F-spec and "forget" to indicate that
it's a 'K'eyed access, you'll get the rows in arrival sequence just as
if you'd processed an unkeyed physical.

-Walden

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 by midrange.com 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.