Re: State of data over the time

Sounds like the ideal situation for a small data warehouse quite honestly. Will this effective date junk that will have to roll around in your database, there is really no good way to do it in the same database without some impact on performance. You should have a history warehouse, and the current info separate if it's feasible. Of course without specific business requirements it's hard to judge.

On Thu, 6 Sep 2001 11:44:06 +0200, "Patrick J." <patrickj_at_kneipN-O-S-P-A-M.com> wrote:

>Hi,
>
>We are currently analyzing an application that will be based on an Oracle
>database. This database will contain about 40 tables, with many foreign keys
>between all these tables.
>An important requirement for this application is that it must be able to
>show the data as it was at any given date and time in the past, this
>concerning every data in the database, and therefore also the links between
>the data. The implementation of this functionality should not compromise the
>integrity of the database (most important point), nor result in too bad
>performances of the application.
>I am looking for the better way to fulfill this requirement, in terms of
>organization of data at the database level. Could you please give me some
>advices, based on your own experience?
>
>Thanks,
>
>Patrick J.
>
Received on Thu Sep 06 2001 - 19:37:30 CDT