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



... describing the same ResultSet of complex queries in diffrent ways, should not change the runtime of queries. If it does, it's no feature - it's a side effect (and could change with every PTF). From the optimizer perspective its difficult to get an estimate for the selectivity of diffrent filters for complex queries. Sometimes it would help to push selectivity to the base layer (drawing subsets of data and join as last operation) - understanding your posts right, that's no option for you.
Changing the optimizer behaviour (QAQQINI) might help for some queries, but might have a penalty for others.
If runtime is critical for these queries, I would think about denormalisation (providing addtitional tables to speed upr special queries). In a BI environment (using the database in read only mode and prevent usage during load) you could refresh the denormalized tables at end of load process. For mixed access (transactional data), the denormalized tables could be held current by triggers.

D*B

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.