Re: problem with historical data and referential integrity
From: -CELKO- <jcelko212_at_earthlink.net>
Date: 9 Dec 2004 07:01:59 -0800
Message-ID: <1102604519.577020.58630_at_z14g2000cwz.googlegroups.com>
Date: 9 Dec 2004 07:01:59 -0800
Message-ID: <1102604519.577020.58630_at_z14g2000cwz.googlegroups.com>
>> Personally I tend to just separate our database in two: one set of
tables containing only current data with full and simple RI
implemented. All historical data goes into separate "_hist" tables with
additional valid_from/to columns and without referential integrity. <<
A classic data warehouse. I tend to leave them in the same table for awhile, with a VIEW that gives the current rows for the application, then move them at the end of the year or quarter to the warehouse. Received on Thu Dec 09 2004 - 16:01:59 CET