|
Booth, One technique would be to determine what window of time is used for most queries to the history data and keep a 2 level history file. When a history record is beyond the time window you select, move it from "current" history to "past" history. This will keep your puts and typical retrievals running against a much smaller file. You can build logical files that merge the 2 history files into a single view for those exception queries. Just create the logicals with *REBUILD access paths and run the queries in batch. Stan -----Original Message----- From: booth@martinvt.com [mailto:booth@martinvt.com] Sent: Thursday, 21 December, 2000 8:44 AM To: midrange-l@midrange.com Subject: accessing the records in a history file I'd like some insight from folks on this scenario: There is a history file of records dating from 1994. Records are added each day and now there are 3.6 million records in the file. The odds of anyone going back to look up something in 1994 are slim but management won't purge any records. Obviously the newest records are at the end of the file. All of the logicals have the customer ID number as the first key. One logical has a key of the customer ID and then date and time. Each business day there is at least one and sometimes five or more reports written for all activity during some recent time period (a workshift, a day, a week, whatever). This process is becoming a performance pig; additionally there is a need for more function. What sorts of suggestions do you people see as possible enhancements to this? SQLRPGLE? OPNQRYF? a new Logical on date and time alone? #GSORT? Any suggestions are appreciated. thanks in advance. _______________________ Booth Martin Booth@MartinVT.com http://www.MartinVT.com _______________________ +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.