Purging gltr_hist

[Chris Kelleher]

First of all, this is for a NON-PRODUCTION system. So don't yell at me for
even suggesting the following ...

Progress 8.3B
IBM RS/6000 running AIX 4.2
MFG/Pro 8.5E


Our AIX development box is becoming pretty crowded - 3 copies of a
production 8GB database. 1 for development, one for testing and one is a
"pseudo-production" report-only-dayold copy.

I decided that we could use the Delete/Archive utilities to remove all but
the most recent 6 months worth of data from the DEV and TEST databases.
Then, do dump/load on these and reduce the disk space used by them.

OK, 3.21.23 has DRASTICALLY reduced the database size. One large file
remains - gltr_hist.
I know I should use 25.13.11 (GL Consolidation), but I really don't care to
even keep the consolidated transactions.

Now, the question...
Instead of consolidating, can I just delete gltr_hist records prior to a
given effective date?
Will this cause referential integrity problems? I don't think it will - the
File Relationships book doesn't indicate a problem will crop up, just want
to be sure.

I would rather do it this way because 25.13.11 takes f-o-r-e-v-e-r to run.
Even when consolidating 1 month at a time.

The gltr_hist table contains 6,738,000 records, total size is 1.1GB.

Reducing from 2.5 years of data down to most recent 6 months:
tr_hist was reduced from 1.6GB down to 654MB.
trgl_det was reduced from 683MB down to 290MB.

I have used several other Delete/Archive programs as well. Total reduction
(so far) is about 3.5GB of data. Nearly half already - if I can quickly
purge the gltr_hist, I'll be set!

Again, this NOT for a production system.

Thanks in advance!

- Tris Hopkins
Flexalloy-Textron

 

[Chris Kelleher]

Tris,

I always believe that play systems are for testing what you'd do in the
real world, so...

I'd consolidate. You can consolidate transactions and then consolidate the
consolidations until the entire two year period is represented by a single
set of GL transactions.

But do yourself a favor, and don't try to consolidate the whole two-year
chunk at once. Do it about a month at a time. Once you've got those 24
months, you can then consolidate them all in one shot.

And for a side note, I'd check your production database to see if you're
still posting GL in Detail. After 2-1/2 years, folks should be comfortable
enough to post in summary, which will greatly decrease the size of your
history.

As for the referential integrity concerns, I'm not sure. What I'd look at
first is the source code cross reference to see where else that table is
used, and I'd also look at the file definition book to understand better
how the application works with other areas.

Good luck.

Scott
===============================================================
Scott M. Dulecki /* 1998061901 */ +1 616 975 6322
Product Manager scott_dulecki@qad.com
QAD, Inc. http://www.qad.com
1188 East Paris SE Grand Rapids, MI 49546 USA

Next Michigan Progress Users Group: 17 November 1999

All opinions are my own, and don't necessarily reflect those of
any other living being.
===============================================================