>
>You should look into why memo is growing so fast. Most likely it's result of to many updates on memo fields. Every time a memo field is updated, it's copied entirely to the end of FTP file (unless table is open exclusively).


I'm aware of what is causing the issue, and I have plans to address that. There's a nightly automated job that updates this table and makes thousands of updates to this memo field. I intended to remove the memo and replace it with a character field of reasonable size, since it isn't critical that the entire contents of the source field be available all the time.

The target table is derived data from other sources put together to streamline some internal data entry and reporting.

For today, I went ahead and restored from a recent backup and rebuilt it.

I'd be interested in strategies used by others to provide a memo-like structure that can be frequently updated without causing bloat.