why we use materialized view over view?
- 1 Answers
- 4484 Views
- Zensar, I also Faced
- E-Mail Answers
Answer / abhinaw prakash
When we issue Select * from View it'll fetch the data from
the Base table were as with Materialized view when we issue
select * from Materialized view it ll fetch the data from
the materialized view.
Also with using materialized view we can escape the run time
joins that it ll have to do when retrieving for a query.
Also with View you cannot schedule it for refresh but with
MV we can schedule it for Refresh
| Is This Answer Correct ? | 3 Yes | 0 No |
In warehouses how many schemas are there?
Explain about Recovering sessions?
explain about informatica server architecture?
Briefly explain the aggregator transformation?
what is confirmed dimension?
What are the basic needs to join two sources in a source qualifier?
What is decode in informatica?
Can we use Union Transformation for Heterogeneous sources? i.e; 3 sources, 1 from Oracle, 2nd from Informix, 3rd from Sql Server with same metadata?
What if we sort the data in descending order instead of increasing order in sorter t/f and send the data in aggregator t/f is there any performance downfall? Please answer below. thank you.
what is runtime variable?
How is Source Side push down optimization different to just providing a SQL override in Source qualifier transformation.
Can anyone please help me out,In which transformations records will be rejected and how capture those records?and How to reload the rejected records?
Teradata 
