If you can't use a DW idea look into Snapshots. If you don't need an up to
the second view of the data that is. or schedule the report run time. Most
reporting packages have the ability to do so.
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent:
Thank you all for your opinions.
The tables that I want to consolidate are 15 Million rows each. So five
tables put together will constitute 75 million rows in one table. I will
have to consider partitioning after that for optimum performance. Also
Materialized view would take a long time to r
t; To: Multiple recipients of list ORACLE-L
> Subject: RE: Database Views
>
> that works as long as you can live with possibly inconsistent data in
> the joint table due to either
>
> 1) updates to the employee data on either site during the day not
> reflected in the joint
This is why data marts were created.
You would be much better off to create a reporting database
based on the data you need to see.
You won't be happy doing this with views from several databases.
It won't perform well. As Rachel pointed out it will be inconsistent.
At the very least you cou
that works as long as you can live with possibly inconsistent data in
the joint table due to either
1) updates to the employee data on either site during the day not
reflected in the joint table until the nightly processing is done
2) nightly process failing and data in the joint table either
Hello Srini
We had a case like this where one of the tables was in a database that
reside in a remote site.
Our solution was to create a table that combine employees tables from 2 site
into one TABLE in the local site.
This way the select and join is done ONCE at night.
Yechiel Adar, Mehish Com
