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:
Computer Services
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Sent: Wed, January 16, 2002 10:05 PM
To: Multiple recipients of list ORACLE-L
Subject: Database Views
I would like get your opinion on what would be the best way provide
:Database Views
I would like get your opinion on what would be the best way provide
access
to data across multiple databases on just on Node (database).
One way that I have tried is create a view on one database that
reads
tables
across remaining four databases using Dblinks. Let us
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
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 table until the nightly processing is done
2
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
I would like get your opinion on what would be the best way provide access
to data across multiple databases on just on Node (database).
One way that I have tried is create a view on one database that reads tables
across remaining four databases using Dblinks. Let us say there is a table
called
