Dxmaint

[Jose Lerebours]

On 10/29/2017 02:13 PM, Richard Kreiss via Filepro-list wrote:
> Situation:
>
> The is a service that rebuilds all of the auto indexes for their order header & order detail files.  This service starts at 4 AM on Sunday and take a long time to run as there are 10 order header indexes and 12 order detail indexes.  Both files have a qualifier and these indexes are also rebuilt.
>
> The primary order header file has 1, 075,176 records and the order detail file has 22.719,170 records.  Most of these indexes are multi key.  The header file rebuilds fairly quickly.  It is the detail file that takes a lot of time.

Have you ever considered normalizing your files, using smaller tables and archiving data?

You really do not need your daily operation files with more than what is "open" not older than 120 days, beyond that, arhive it.

So, given an sales order module where:

dailyOrdersh is archived to dailyOrdersha
dailyOrdersd is archived to dailyOrdersda

In doing so, you can basically rebuild indexes on your daily operations files in matter of minutes since your combined records of 3+
millions should shrink to a few thousands (even if as many as 100K records, you will be way ahead of the game).

Just because you can keep millions of records in a file does not mean it is a good idea to do so.

All that said, a replica of your existing code should be good enough to grant access to archived records so, there should be very little
work from your part to get this done and have a solid long term solution to your problem.

Finally, I wonder if @menu show "@File not available due to daily maintenance!" could help after checking dow() ... and a predictable
time frame you want to safe guard ... !?!