Re: Long term database archival

> I am not to sure of the relevance, but I periodically worked as a
> sub-contractor for an
> Oil-producing Company in California. They were carrying 35 years of
> data on an Alpha Server
> running Ca-Ingres. The really bad part is that hundreds and hundreds
> of reporting tables were
> created on top of the functioning system for reporting over the years.
> Now nobody know which
> tables are relevant and with are redundant and or deprecated.
>
> Also year after year, new custom text file reports were created with
> procedural scrips. The load
> on the server was such that the daily reporting was taking near taking
> 23 hours to complete. And
> the requests for new reports was getting the IT department very
> worried.

But the data from 35 years ago wasn't stored in Ingres and, if it's
important, it won't stay in Ingres. The data shifts from format to
format as technology progresses.

It seemed to me that the OP wanted some format that would be readable
in 20 years. No one can guarantee anything like that.

-M

¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬
AgentM
agentm(at)themactionfaction(dot)com
¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬