|
>>It sounds like the optimiser has to >>re-create the access plan. >>Is there dynamic SQL in the program? >Yes there is... Hi David! You are entering the realm of Performance Tuning. It's so easy to write SQL that we often lose sight of what we're asking the machine to do for us. Dynamic SQL makes the most demands on the system and provides it with the fewest clues on how to optimise. If at all possible, get rid of the dynamic SQL and replace it with parameter markers. You'll have to get used to the answer 'it all depends...' when talking about performance, because each site is different; number of files, records, relations, indices, views, etc. all play a role. The prime performance factor is having a good index already built. Read the performance section of the SQL Programmer's guide and you'll start to get a feel for the task. Run your program in debug to see optimiser messages in the job log. I wish I had a good answer to give you, but this is one of those things that you're going to have to work out for yourself, with your own database. --buck
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.