Indexes are for performance enhancement. For example, let's say your
table is really large. And you use that view. If you look at the system
index advisor it may recommend creating an index over the table by that
column. You might never directly access that index but it may help
performance.

The problem you are having with trying to combine an index and a few is
that indexes aren't meant to be quite that dynamic. Newer versions of the
OS support where by clauses and other interesting matter in an index. For
example, you can have WHERE STSCODE='A' in an index. Much of this was
built to allow sql to define a much larger percentage of the logical files
created by DDS than it could previously. However an index still has to be
geared towards performance. Doing an index by current date would be no
different than creating an index by STSCODE and expecting it to be by 'A'
one day, by 'Z' another and by 'R' the next. Normally not even a business
case for such a beast but that's not my point. The point is that it's
harder to really only select down those records and then automatically
change the criteria at break of day and still get the performance wanted.


Rob Berendt

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2019 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].