Hi,

We have an application that manages gasoline stations. Our biggest table is
a log table,
that logs every transaction that happens on the forecourt. We used to have
this all in dBase
tables, and we had to back up the tables to external files or tables every
three months or so.

After moving our db to Firebird, we no longer do any such archiving. We need
to keep historical data for a period of 5 years or so. We keep it all in
the database,
and back up the entire database periodically.

So my answer is : why, when running a RDBMS, do you need to archive at all?
We run at about
30 000 transactions per month in the log table, and we have no problems
with that kind of
transaction density.

HTH

Tim

At 11:53 AM 14/10/2004, you wrote:

>Hi,
>
>Could you share with we, what expiriences do you have with making archives
>of some table data ?
>
>Let me be more specific:
>in an application with clients, orders, employee an similar stuf there can
>be a few houndreeds or more orders each year.
>Normaly we do not need to have all orders in actual orders table, but we
>should be able to check any old order at any time.
>So old orders should be transfered to another table with the same data
>structure as actual one.
>
>What approach do you prefer ?
>Make just a new table within same database (fdb file) or is better and more
>secure to create separate database (fdb file) just for archive.
>
>I don't have in mind backing up my data, but exclude old orders from actual
>orders table.
>
>
>Regards,
>Primoz
>
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>