RE: Indexing an SQL view -- MIDRANGE-L

× 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.

Tom

I may have not been clear enough - the index is actually the LF itself - key fields (K-specs) over the new calculated fields. An SQL index cannot be created over an LF, as I just checked.

But this is what we tools vendors are about, right? Selling things that help people manage the increasingly unmanageable.

Regards
Vern

At 10:02 PM 4/19/2004 -0400, you wrote:

midrange-l-request@xxxxxxxxxxxx wrote:
>   1. RE: Indexing an SQL view (Vern Hamberg)
>
>Fortunately, Rick reports improvement.   ;-)
Yes, 'fortunately'. From some of the threads recently, I'm getting the feeling that educated DB2 DBAs are becoming more important. It seems that few are willing to assert "THIS is how it should work." As much as I recognize that environment significantly changes results, revelations such as the need for SQL INDEXes rather than keyed LFs seem to come out of nowhere. (Surprise!)

A DBA supposedly could keep up. But generalist programmers have far too much in too many areas to keep up with. I've long been aware that SQL VIEWs over other VIEWs and even over LFs let you do some pretty slick stuff. But it never occurred to me to INDEX a LF -- much less grasp the implications if there are any.

Tom Liotta

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.