|
Evan, I would opt for scenario no. 1: Populating the physical file and 'over time' create those logical files. Maybe you don't need to have ALL those 20 logicals created at once. The first logicals I would create would be the ones to be used immediately. Then, off-hour, off-peek or whenever I would create the rest (trying to balance the computer work). Also I would try to find out how many of those would be candidates to "share access paths" and create the most significant ones first. That's my view! Leo Evan Harris wrote: > We are about to embark on an exercise that will populate a *large* > database file (40 million records plus). This file has about 20 logical > files built over it. > > My question is, which is more efficient: > > 1. Populating the file and building the logicals ? > > 2. Building the logicals and populating the file ? > > Any thoughts would be greatly appreciated. > > Cheers, > Evan Harris > +--- > | 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 > +--- -- Leo Lefebvre leo@tug.on.ca Toronto Users Group for Midrange Systems Visit our home page at <http://www.tug.on.ca> Ph: (416) 606-5960 --- Fx: (416) 495-0100 +--- | 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.