Answer / harshakore

A view has a logical existence but a materialized view has
a physical existence.Moreover a materialized view can be
indexed,analysed and so on....that is all the things that
we can do with a table can also be done with a materialized
view.

Answer / senthil

hi,
we already know basic restrictions of view and materialized
view,

view is a logical or virtual table it doesn't have data on
its own, but materialized view has a physical structure it
stores data in local machine or on its own.materialized view
can be refreshed automatically or manually. but in view, if
any changes happened in the base tables, we want to reflect
the same in the view means view has to issue the select
statement again to the database

Answer / anju

A materialized view is a stored summary containing pre-
computed results.As the data is pre-computed, materialized
views allow for faster query answers

In warehousing applications, large amounts of data are
processed and similar queries are frequently repeated. If
these queries are pre-computed and the results stored in
the data warehouse as a materialized view, using
materialized views significantly improves performance
by providing fast lookups into the set of results.

A Materialized View generally behaves like a Index and it
can also have any Number of Aggregates and Joins.

Answer / papa

Materialized View caches the data,but view cannt store the
data all.

Answer / navas

View:It is a sql query which is executed and populates
results each time when the particular view is accessed.When
we make a DML statement in view it will affect the original
data available in datebase table.
Materialized view:Materialized view is similar to a table
that exists in the table space.The resultsets are fetched
and populated in materialized view from various table when
a meterialixed view is created and will be availabe until
the view is refreshed.

Answer / roshan

apart from all the above answer one more difference is:
suppose we delete a table then all the views becomes invalid but this is not the case with the materialized view. its most interesting feature is auto commit refresh...

Answer / surajit n bhowmick

A View is just a stored query and has no physical role.
Once a view is instantiated, performance can be quite good,
until it is aged out of the cache.

A materialized view has a physical table associated with
it, it does not have to resolve the query each time it is
queried. Depending on how large the result and how complex
the query, a materialized view should perform better.

Answer / manohara reddy

view is logic and virtual table. it does't hold data.it
allows DML Operations.when ever u update or insert in base
table or view automatically changed those.
materialized view is static. u want create m.view DBA
Privileges and permissions must. it hold data all. when ever
u update or create rows in base table , it update only
update base table. doesn't change.

Answer / tiklu

Materialized Views are used by men with Tiny Penis
Where are Views are for Women with loose Vagina

Answer / the tiklu

Materialized View is for Consumerist es, while Views
are for great men and sexy women.

can v update d records in target using update stargey without generationg primary key ? explain

4 Answers   CTS,

Hi, I am working on informatia in a support role. We used stored procedures in informatica and other than that I never got a chance to work on PL/SQL,little on Unix scripts. But I heard people asking about PL/SQL alot. Can any one let me know how do we use PL/SQL with informatica and if required what is the knowledge that we need to have on PL/SQL? Please let me know in detail which would really help me alot in my career prospectus.

1 Answers   Accenture,

difference between informatica 8.1.1 and 8.6? And different betweeninformatica 7x and 8x?

1 Answers   HTC, TCS,

If i havee 3records in my source having same deptno like Deptid Deptno ------ ------ 101 10 201 10 301 10 and i am using router TR to loading these records into target.Then how many record'll be loaded into target???

5 Answers   Wipro,

Are there any types of Dynamic Caches in informatica

4 Answers   Accenture,

Explain scd type 3 through mapping.

0 Answers  

i have flat file it contains 'n' number of records, i need to send half of the records to one target table and Remaining half to another target table: pls full details

8 Answers   L&T, TCS, UnitedHealth Group, Wipro,

CANNOT USE PARAMETER FILE! Hi all, I am trying to use parameter file for my workflow. This could help me to filter records where CITY = 'Portland' Following is what I have done: **in Designer - create new parameter : $$PARA_FIL, Parameter, String, IsExprVar=TRUE, Initial value = [empty] - Source Qualifier/ Properties/Source Filter: CUSTOMERS.CITY='$$PARA_FIL' **Create Parameter file: C:\Informatica\PowerCenter8.6.0 \server\infa_shared\BWParam\DynamicParamTest.txt $$PARA_FIL='Portland' **Configure workflow to use the parameter file: Edit Workflow/Properties/Parameter Filename: C:\Informatica\PowerCenter8.6.0 \server\infa_shared\BWParam\DynamicParamTest.txt I also configured directory of parameter file for session task. However, I just got this in the session log: [SQ_CUSTOMERS] SQL Query [SELECT CUSTOMERS.CUSTOMER_ID FROM CUSTOMERS WHERE CUSTOMERS.CITY='$$PARA_FIL'] No record has been loaded to target. It seems that the parameter file has not been read. I cannot understand the reason why. Could any of you kindly suggest me anything? Thanks

4 Answers   CSC,

Where are the source flat files kept before running the session?

0 Answers   Informatica,

we have to use order by,where,having we to implement sql query

1 Answers   Satyam,

What is informatica? What exactly are the practical uses in real world

2 Answers  

Is stop and abort are same in informatica?

0 Answers