|
Generally speaking, naming a logical file in a SELECT does not bias optimization to use it. However, it looks like yours is a select/omit logical, and then I'd say go ahead and use it. You basically have a WHERE clause there, in the S/O statements of the logical file. At 06:33 AM 6/14/02 +0000, you wrote: >Consider we have a physical file with 500,000 records and a logical file >based on this physical file with 200,000 index entries. We have the >required set of records available through the logical file. > >My question is, the SQL query processing time is less if we use logical file >in the SQL query. Is there any standard like, it is better to use a physical >file in any SQL query? If yes, why should we use a physical file instead of >a logical file eventhough we have the required data >available through the logical file's access path? > >Any feedback is greatly appreciated. > >thanks. > > > >_________________________________________________________________ >Send and receive Hotmail on your mobile device: http://mobile.msn.com > >_______________________________________________ >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.