|
Until it's not.......
If you have heavy SQL, them that setting can, not always certainly, and usually does, bollox things up. It forces the optimizer to run for every query. Sometimes it'll do a table scan, other times it'll build an index. It may or may not use existing index objects.
Mean time you're sitting there trying to understand why things run differently every day.
Bottom line is, performance is as much art as science, and a solid understanding of the application is a good starting point.
Jim Oberholtzer
Agile Technology Architects
On Nov 30, 2018, at 12:19 PM, Roger Harman <roger.harman@xxxxxxxxxxx> wrote:
When I had that responsibility, I just set QPFRADJ to '3' and was a happy camper. Figured the machine was smart enough.
Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power
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.