Answer / sreenu329

One of the most interesting and valuable dimensions in a
data warehouse is one that explains why a fact table record
exists. In most data warehouses, you build a fact table
record when something happens. For example:

When the cash register rings in a retail store, a fact
table record is created for each line item on the sales
ticket. The obvious dimensions of this fact table record
are product, store, customer, sales ticket, and time.
At a bank ATM, a fact table record is created for every
customer transaction. The dimensions of this fact table
record are financial service, ATM location, customer,
transaction type, and time.
When the telephone rings, the phone company creates a fact
table record for each "hook event." A complete call-
tracking data warehouse in a telephone company records each
completed call, busy signal, wrong number, and partially
dialed call.
In all three of these cases, a physical event takes place,
and the data warehouse responds by storing a fact table
record. However, the physical events and the corresponding
fact table records are more interesting than simply storing
a small piece of rev enue. Each event represents a
conscious decision by the customer to use the product or
the service. A good marketing person is fascinated by these
events. Why did the customer choose to buy the product or
use the service at that exact moment? If we only had a
dimension called "Why Did The Customer Buy My Product Just
Now?" our data warehouses could answer almost any marketing
question. We call a dimension like this a "causal"
dimension, because it explains what caused the event.

Answer / sreenu329

One of the most interesting and valuable dimensions in a
data warehouse is one that explains why a fact table record
exists. In most data warehouses, you build a fact table
record when something happens. For example:

When the cash register rings in a retail store, a fact
table record is created for each line item on the sales
ticket. The obvious dimensions of this fact table record
are product, store, customer, sales ticket, and time.
At a bank ATM, a fact table record is created for every
customer transaction. The dimensions of this fact table
record are financial service, ATM location, customer,
transaction type, and time.
When the telephone rings, the phone company creates a fact
table record for each "hook event." A complete call-
tracking data warehouse in a telephone company records each
completed call, busy signal, wrong number, and partially
dialed call.
In all three of these cases, a physical event takes place,
and the data warehouse responds by storing a fact table
record. However, the physical events and the corresponding
fact table records are more interesting than simply storing
a small piece of rev enue. Each event represents a
conscious decision by the customer to use the product or
the service. A good marketing person is fascinated by these
events. Why did the customer choose to buy the product or
use the service at that exact moment? If we only had a
dimension called "Why Did The Customer Buy My Product Just
Now?" our data warehouses could answer almost any marketing
question. We call a dimension like this a "causal"
dimension, because it explains what caused the event.

Answer / dipali

amazing explaination...thanks a lot

Answer / sorna kumar muthuraj

Interstingly i noticed now only it is not casual... it is
CASUAL dimension... Now the name makes more sense with the
explanation... Cool Explanation dude...

Answer / anonymus

good copy of the link :)

http://www.kimballgroup.com/html/articles_search/articles199
6/9611d05.html

Answer / bsgsr

i sincerely appreciate ur interest n moreover ur patience
in explaining so beautiful. thanks a million for ur ans.
can i have your mail id or number pls.
here are mine.
9866188658 bsgsr12@gmail.com

Explain lookup transformation in informatica

0 Answers   Informatica,

Where should yoU place the flat file to import the flat file defintion to the designer?

4 Answers  

Data transformed successfully from Source table to target table. Now how you will ensure that the data in Target table is proper. I answered will verify one or two records and check Then question was that the Development is doing (1-2 record verification)but as a tester you have to verify the complete data, how you will do?? Please answer

2 Answers  

Which means the first record should come as last record and last record should come as first record and load into the target file?

0 Answers   Informatica,

What is the difference between Junk and Confirmed Dimention? where can be used htat one in Informatica?

3 Answers  

How do you implement scheduling in Informatica?

1 Answers  

I am having a table with columns ID NAME 1 x and the requirement is to get the o/p like this 1 y ID Count(*) 1 z 1 3 2 a 2 2 2 b 3 c so write a sql query to get the id n how many times its count of repetition n there u shouldn't get the distinct(i.e id-3) Reply as early as possible

3 Answers   IBM,

Source --------- eno , ename, sal 001,ank,1000 002,behe,2000 003,raj,2500 Target ------- header :DDMMYYYY24MMSS timestamp body: 001,ank,1000 002,behe,2000 003,raj,2500 footer: count(eno),sum(sal) how to implement the same in a FF tgt?

2 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,

without dynamic lookup how to insert new rows and update existing rows?

1 Answers   HP,

What are the joiner caches?

3 Answers   Informatica,

What is meant by target load plan?

0 Answers