I have two tables TABLE1 and TABALE2 which I joined and build a query. Now the data fetched with this query I need to insert or update(if record already existing) into a table TABLE_REP which is in another schema but same database.
First time I need to load all the data after that for every week I need to load the data into the new table TABLE_REP. For a week data may be appx. 10 million records.
One way is we need to write a Stored procedure and schedule for every week after the first full load.
Can you please suggest is there any other better way?
Can we use Materialized view and schedule it for every week after the first complete refresh? In this way can we track and log any failed records in any log table?
Also I need to archive the data from the TABLE_REP table for older data into another table and delete from this table. So if I use Materialized view can I achieve this also?
Like this I have 10 reporting tables for which data needs to be fetched for every table with 2 base tables joining from another schema.
Which option is better out of these two approaches (stored proc and MV)?or Is there any better approach also other than these two options? Request you to suggest.
Select from freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely and get projects done right.
From the Oracle SQL Reference (http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/queries006.htm) we are told that a join is a query that combines rows from two or more tables, views, or materialized views. This article provides a glimps…
Why doesn't the Oracle optimizer use my index?
Querying too much data
Most Oracle developers know that an index is useful when you can use it to restrict your result set to a small number of the total rows in a table.
So, the obvious side…