Question { TCS, 18837 }

checkout and checkin in informatica 8.6

Answer

Check out & check in are users locks over WF/Session/source
or target .A user has to checkOut a object for any
modification. If the object is checked in it cant be
modified.any changes done by checking out will reflect on
server only ofter checking in...we can run a wf at any
state irrespective of whether it is checked in or out

Question { 5961 }

is it sufficient to normalize a database up to 3NF?

Answer

It all depends on users aproach towards data
selec/inserts/updates
... Normelization affects data retrival severely.
we can go up to BCNF

Question { TCS, 7169 }

TELL ME ABOUT WORK FLOW SCHEDULING?

Answer

There are many Job scheduling tools available
like
Autosys
Control M

we can even schedule in pmcmd or by right clicking wf

Question { 3i Infotech, 5325 }

1)what is the difference between view and materilized view?
2)what is the difference between delete and truncate?
3)what is the difference between migration and upgration?
4)what is the difference between RMAN HOT BACKUP and normal
hot backup?

Answer

2)Truncate is a DDL command, which has autocommit hence
cant be rolled back where as delete is DML with user commit
& roll back option. Truncate is faster then delete since it
wont store any data to backup tablespace. before delting.

Question { 3i Infotech, 5325 }

1)what is the difference between view and materilized view?
2)what is the difference between delete and truncate?
3)what is the difference between migration and upgration?
4)what is the difference between RMAN HOT BACKUP and normal
hot backup?

Answer

1)views , Materialized view or summary tables are subset of
a table filtering out uninteresting rows and columns.The
difference is that views are logical where as MV's are
actual tables.Views pulls real time data when ever queried
but data in MV is rfereshed based on users need.also when
you query a materialized view, you are querying a table,
which may also be indexed. In addition, because all the
joins have been resolved at materialized view refresh time,
you pay the price of the join once (or as often as you
refresh your materialized view), rather than each time you
select from the materialized view .Materialized views are
most often used in data warehousing / business intelligence
applications where querying large fact tables with
thousands of millions of rows would result in query
response times that resulted in an unusable.

2)

Question { TCS, 4767 }

write a query to follwoing table

amount year quarter
254556 2003 first
546332 2003 second
129034 2003 third
490223 2003 fourth
165768 2004 first
265443 2004 second
510412 2004 third
435690 2004 fourth

i want the output

year q1_amount q2_amount q3_amount q4_amount
2003 254556 546332 129034 490223
2004 165768 265443 510412 435690

Answer

Select YEAR,SUM(q1_amt)q1_amt,SUM(q2_amt)q2_amt,SUM(q3_amt)
q3_amt,SUM(q4_amt)q4_amt from (
select YEAR,
Decode (QUARTER,'first',amount,0) as q1_amt,
Decode (QUARTER,'second',amount,0) as q2_amt,
Decode (QUARTER,'third',amount,0) as q3_amt,
Decode (QUARTER,'fourt',amount,0) as q4_amt
from table_name) group by YEAR