×
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.
More queries are going down SQE query engine, which may mean that you have
to do some additional database and SQL performance tuning with that query
engine in mind.
Keep in mind that with the new OS, all access plans on the systems are
recreated. Most for the better, but some for the worse (temporarily
anyway).
Building 'perfect' SQL indexes will do wonders for your database query
access. And it's not just set it and forget it type of activity. As you've
found, things change (i.e. the OS upgrade) and you have to revisit your
indexing strategy.
Elvis
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com
-----Original Message-----
Subject: unexplained performance problems with SQL after upgrading to V5R4
Hi, all:
One of our large customers upgraded their production system from V5R3 to
V5R4 last week-end.
They re-initialized all of their DASD and re-loaded all of their data
from back-up tapes, during or after the upgrade to V5R4. They say access
paths were saved (and restored), so they are not seeing index rebuilds
going on.
The problem is, for their applications that use embedded SQL, they are
seeing much slower performance, versus what they saw a week ago, when
they were still running on V5R3.
Does anyone have any ideas about where to look, or what to look for?
Perhaps some values changed in QAQQINI?
Thanks in advance for any suggestions, hints or tips.
Regards,
Mark S. Waterbury
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: unexplained performance problems with SQL after upgrading to V5R4, (continued)
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.