|
Mike, If you have the time available to process a reorganization to purge deleted records, then there should be no downside except for the relative record number processing disaster mentioned in a previous post. I'm assuming that this is a one-time kind of thing you're doing because you want more disk space, and not a weekly process you're going to implement in production. Some thoughts: - If you have applications that process your database by relative record number, then a reorganization could break the whole thing. This is an older style of processing and is not often found in newer applications. A system which does this type of processing should have its own set of utilities for reorganization. - If your files are very large, I would not attempt to resequence them by key unless you have a lengthy amount of time available. Just do the purge, get your space back, and leave the order as is. Regards, Andy Nolen-Parkhouse > On Behalf Of Mike Berman > Subject: File Reorg - Cons > > I noted alot of suspicion when I attempted to set up a file reorg process. > Just getting lists of those with large amounts of deleted records. Is > there some possible occurance that would be a detriment? I am of course > referring to off hours running.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.