|
Posted for a colleague:
What I was told: A SEQUEL select statement is run over a very large (50-60
Million records), select by name and a plan field. MOST of the time results
are returned quickly but for "some" names the statement does not use the
existing index and thus creates one, which causes about a 20-30 minute response
time. IBM support to date has not been able to help and they ahve submitted a
PMR to IBM but no response yet and it is becoming (is) an issue.
Example:
Name=Smith Plan=B, quick response
Name=Jones Plan=C, takes forever
I was told that they have also tried it as a straight interactive SQL and get
the same issue. They have not been able to find any rhyme or reason as to why
"some" names/plan combinations take so long. Anyone run across this or have
any ideas?
---------------------------------
Yahoo! Music Unlimited - Access over 1 million songs. Try it free.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.