Answer Posted / 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.
Is This Answer Correct ? | 9 Yes | 2 No |
Post New Answer View All Answers
How you prepared reports for OLAP?
Where are the source flat files kept before running the session?
I have a flat file, want to reverse the contents of the flat file
What are the designer tools for creating transformations?
What is informatica worklet?
How do you load alternate records into different tables through mapping flow?
Name at least 5 different types of transformations used in mapping design and state the use of each.?
What is a repository manager?
How can repository reports be accessed without sql or other transformations?
Explain the informatica workflow?
Performance tuning( what you did in performance tuning)
If the source has duplicate records as id and name columns, values: 1 a, 1 b, 1 c, 2 a, 2 b, the target should be loaded as 1 a+b+c or 1 a||b||c, what transformations should be used for this?
What is meant by pre and post session shell command?
Calculate sum of salaries department wise. Then the sum will be repeat for all columns in each department. Develop a mapping for this.
What is aggregate cache in aggregator transformation?