Subject Re: [firebird-support] Historic tables design
Author Aldo Caruso

Your strategy is interesting. Keeping the historic records in a
table in a different database sounds smart, as it helps keeping the main
database away from growing indefinitely.

Nevertheless, troubles arise if you have to query the historic
table, making joins with look up tables wich reside in the main
database. Firebird doesn't allow queries between tables belonging to
different database, and so you'll be forced to replicate lookup tables
in the historic database as well in order to display them accordingly.

Keeping the historic table in another database may be a good idea,
but it depends on what you have to do with the historic records. It is
fine if you only have to keep them for backup or legal concern and don't
have to show them in you application joined with current look up tables.

Aldo Caruso