|
Vern,
The way I read the post,
The original job took 30min.
He added a step containing SQL, and the job took 3hrs.
He added the index and the entire job then took 5min.
His question, why does the job now run so much quicker than originally
when only the new step contains SQL.
My answer:
he's either wrong about other steps in the job not containing SQL
and/or other query activities; or there's something else besides the
new index coming into play.
Perhaps I'm misunderstanding but...
Charles
On Tue, Sep 23, 2008 at 8:09 AM, wrote:
There is an SQL process, I believe - David said he "added an SQL request" - Isuspect he meant query - probably same or similar word in French. And he said
the job got very slow after adding it.
it,
-------------- Original message --------------
From: "Charles Wilt"
David,
As a new SQL index ( or DDS logical ) for that matter would only
effect SQL statements or an RPG program that used them directly (via a
f-spec), I'd have to say you are incorrect in saying that no other
part of the job used SQL ( and/or for example OPNQRYF, query/400 or
query manager reports)
Otherwise there's something else coming into play.
Charles
On Tue, Sep 23, 2008 at 4:50 AM, David FOXWELL wrote:
Hi,certain circumstances. In fact I'd added an SQL request on a PF without
I had a complaint that a job was taking nearly 3 hours to run at night in
realizing the consequences. The job already took a long time before I added
themaybe half as long.
Anyway, I used the iNav index advisor to create the necessary index. Now,
thejob runs in 5 minutes! I am wondering why it is so much faster than before I
added the lengthy SQL request?
I can't find any other SQL references in the job. RPG programs are using
anPF with a CHAIN operation. I have replaced the index I created with iNav with
7LF and it runs just as fast. The same PF with about 2 million records now has
?LF.
references it. How should I prevent someone from cleaning up and removing it
Also, as my new LF is only currently used in my SQL request, there are no
------
TIA.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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.