I'm right to say you really don't need oracle materialized views? and we can do it manually?
Date: Mon, 1 Aug 2016 16:57:31 -0400
Message-ID: <CAGYrQytdNUJUdyL4KXB6ZoHouK43nsjSUFG9qnNSr8gzg=Yi4w_at_mail.gmail.com>
The free feature for Oracle to create materialized views in all release <http://oraacle.blogspot.com/2016/08/the-free-feature-for-oracle-to-create.html>
Hello I'm asking if I'm right please.
I'm not sure, if we really need a special feature to create materialied
views, if we use an obvious methodology to create a materialized views like
this, we cna see we cna creaet even an option to update teh materialied
view from a trigger.
I dont understand clearly why to user oracle materialized views, to create
a materialized view, unless for standard and time saving, but at the end is
the same.
Because in this way we have more control of everything. Of course there are
more options but we cn add for ourselves.
Thank you :)
First we have the select, of one or more tables; and the table to store it Second we create a procedure that insert the query in a table Third we update it
- if we want a transactional update, we create a procedure that inserts the values for the new records in the trigger of the tables
- if we want a log fast refresh, we create a log that stores id of records we want to be updated
- if we want a full update, we create job Fourth For the update process depending the option we have to create a procedure, add to the trigger/job and that all. Fifth Aditionally we have a validation procedure that periodically if he found differences can generate a full or partial refresh.
First
Create a package
XXX.PCK_MV_OWNER_TABLE
Procedure:FullRefresh
insert into table
select from tableA,tableB
- note in this refresh you can put
Procedure:PartialRefreshperTrigger
This must be in a trigger update and or delete
insert into table
select from tableA,tableB
where column=:new.value and column2=:new.value2
Procedure:PartialRefreshperFunction
insert into table
select from tableA,tableB
where not exists in table
Procedure:PartialRefreshperFunction using log This requires a table that stores ids of modified rows, and a trigger that inserts the rowid when the needed columns of the table are modified, and generates a refresh only of those records in the database.
insert into table
select from tableA,tableB
where not exists in table
Procedure:fast refresh fast
delete from;
FullRefresh;
Procedure:fast refresh online
truncate table;
FullRefresh;
Procedure:validation
with
a select from tableA,tableB
b select fro mtable
select count(*) from
(select from a
minus
select from b
union all
select from b
minus
select from a)
if count>0 then
fullrefresh; -fast or online it dependes on you
end if;
/
Jobs
create job executes validation periodically, depending the tables, etc.
create job if using log to update the materialized view periodically
optionally, create jobs makes partial insert, to reinforce validation.
optionally, makes a full refresh
:)
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Aug 01 2016 - 22:57:31 CEST