> Paula Bennett-Leung wrote:
> 
> I am looking for anyone who has some words of wisdom about data
> archiving.
> 
> We have an ingres database with aging data that needs to be archived,
> but our users have the requirement to be able to view this archive data
> online. The problem I see with this is that our current application is
> written in vision, which means that if the archive data is not kept
> within the database that we cannot use vision to view this data online.
> This in my opinion defeats the purpose of archiving the data if you
> cannot remove it from the database.
> 
> My management also has the requirement of not wanting to spend alot of
> time accomplishing this task. Have it done in less than 30 days.
> 
> Has anyone been in a similiar situation? And is there a successful
> solution?

A simple solution would be to 

Allocate a data location for archive data (new disk if necessary)

Create archive tables (production tables + column archive_date) on this 
location (production table + _hist). Use compression if performance is 
not critical. 

Write some sql scripts to dump the data from the production tables to the 
historic.

Don't forget to dump data from these tables after a period of time.

It would be much better to have the historic information on its own 
database on its own machine. I don't get your point about vision - I'm not 
overly familiar with it but I sure you can call an application that will 
connect to another database. It was possible in ABF.

Con

Ingres Q & A

To William's Home Page

© William Yuan 2000

Email William