|
This step is unclear to me. The control file has a key? That key is in each of the million-plus records? How often will the value of the Control File Key change? I understand that the changes may occur randomly but if the control file has a relativly lower record count then many of the chains might be going for the same record just returned. Is it possible that the greater gain might be to save the Contol File Key, and only chain if the Control File Key is different? --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@MartinVT.com --------------------------------------------------------- -------Original Message------- From: midrange-l@midrange.com Date: Friday, November 22, 2002 09:08:58 AM To: 'midrange-l@midrange.com' Subject: %lookup vs. chain This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] I'm just noticing that as I spin through some large files that I'm chaining out a million times (actually more) to a control file to check a flag. In the initial subroutine I'm setting up an array that I could easily store this flag in. I'm wondering what the opinion is as far as performance-wise which is more efficient, doing the %lookup() on the array or chain to the file? Thanks in advance. Mike _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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.