|
Frank, I do not think it will help to rename the file in the query, as the SQL optimizer will still select its best access path, whether you tell to use that certain file, or whether it exists, at all. I think the SQL optimizer will still look at the PF, if you supply the name of the (correct) LF/index; perhaps another reason fort the bad performance, escpecially large PFs). My policy is to name the PFs in the query and let's the optimizer do its job. It might help to create a suggested LF/index, though. Just my thoughts. Regards, Carel Teijgeler. *********** REPLY SEPARATOR *********** On 21-4-05 at 10:51 fkany@xxxxxxxxxxxxxxxxxx wrote: >For who ever wants to read it here's parts of the job log that show the query >optimizer messages: >(If interested in seeing all the messages, just let me know and I'll post it.) <SNIP> (The query appears to have chosen it's own access path instead of the access path I specified >in the SQL statement. I guess I'll have to change my SQL statement to use the >same access path.)
As an Amazon Associate we earn from qualifying purchases.
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.