Yep... and there is currently an APAR (not yet fixed) for incomplete
expiration handling;  if it's for long-term storage, (like 7 years) but you
only do it once a year, then archive may be your answer... maybe to build
tar files for each file system and archive them instead of the thousands of
little files (and their directories).

Also, there are business that specialize in helping companies store large
quantities of financial records from databases, like Xios;  they store the
data in common-ASCII formats so they can be readable (read "import-able")
back into a later generation database environment from the one that
originally held the data.

Don France



 -----Original Message-----
From:   Richard Sims [mailto:rbs AT BU DOT EDU]
Sent:   Monday, November 13, 2000 9:02 AM
To:     ADSM-L AT VM.MARIST DOT EDU
Subject:        Re: Archiving and database growth

>Thanks - but my question is, how does the database grow for archiving -
does
>it grow the same way as backups?

Basically, yes... See Estimating and Monitoring Database and Recovery Log
Space Requirements in the server Admin Guide.  But consider the pesky
Description field, which per Andy's SQL document can consume up to 255
characters per file by itself, if exploited.
   Richard Sims, BU