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

case and like function in informtica (my source is XML). case when OS Like'%Windows%' and OS Like '%200%' then 'Windows 200' case when OS Like'%Windows%' and OS Like '%200%'and OS like '%64%' then 'windows 200 64 bit' etc.,,

1 Answers  

I have source table 100 records after run session successfully but loads the target table 50 records only what happened that 50 records and how can i load remaining 50 records

5 Answers   Patni,

what are the types of facts with Examples?

3 Answers  

Name the different lookup cache(s)?

0 Answers  

Source (Flatfile) - Target (1-1 mapping). How to load first or last 20 record to target?

5 Answers   Flextronics,

My i/p is like below 1,2,3,4,5,6,7,8,9,10....100 I want that to be populated in two o/p as below o/p-1: 10,20,30,40,50,60,70,90... o/p-2: 11,21,31,41,51,61,71,81,91.... How to do it in ingotmatica...

2 Answers   Accenture,

What is router transformation

4 Answers   CSC,

how many tasks are there in informatica ?

15 Answers   DELL, iGate, TCS,

In Lookup transformation a sql override should be done and disable the cache how do you do this procedure?

2 Answers   Wipro,

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

3 Answers  

Major difference between SQL override and Lookup Sql override

1 Answers  

What are mapping parametres and variables in informatica?

6 Answers   TCS,