|
If I already have SQL indexes existing on my system, is there any notable reason not to replace them with EVI's? Since the system must already maintain the existing index, wouldn't the overhead associated with maintaining the EVI be somewhat similar to maintaining the existing index? The fields used to create the EVI would be identical to the existing index. The only difference is that it would be (re)created as an EVI. Wouldn't this be of benefit if it were only to reduce the physical size of the index? (And I'd think the EVI would be faster too). I'm running V5R2. Comments??? Regards, Jerry Gerald Kern IBM Certified AS/400 RPG IV Developer & RPG IV Programmer MIS Project Leader, Lotus Notes/Domino Administrator The Toledo Clinic, Inc.
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.
midrange.com
