-
I would like to know what is the impact of building a materialized view with refresh fast on commit on database.
i am trying to build a Materialized view from a table which has about 100 thousand rows and there are about 12 columns in the base table and i am pulling out only 3 columns from the base table to build the view,but i have different calculations on the three columns which again turn out to be 10 different columns,
there are no huge data types in the base tyble like blob or long raw.they are all numbers anbers and dates and characters less than 100,
if i have refresh fast on commit is that going to slow down my database...
thanks in advance
Radhakrishnan.M
-
Depending on how offen the users on the other database are going to perform commits. If it is done roughly at every few minitues, yes, If the commits are sparesed out, then you would be fine. If you application requires this amount of concurrency, then go for it, else, do it at a regular intervals
Sam
Thanx
Sam
Life is a journey, not a destination!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|