Guest

• Jan 19th, 2006

 

Based on the requirement to your fact table, choose the sources and data and transform it based on
your business needs.  For the fact table, you need a primary key so use a sequence generator
transformation to generate a unique key and pipe it to the target (fact) table with the foreign keys
from the source tables.

Please correct if I am wrong.

srikanthpatel

• Jan 21st, 2006

 

we use the 2 wizards (i.e) the getting started wizard and slowly changing dimension wizard to load the fact and dimension tables,by using these 2 wizards we can create different types of mappings according to the business requirements and load into the star schemas(fact and dimension tables).

gazulas

 Profile Answers by gazulas Questions by gazulas

• Jan 29th, 2006

 

first dimenstion tables need to be loaded, then according to the specifications the fact tables should be loaded. dont think that fact tables r different in case of loading, it is general mapping as we do for other tables. specifications will play important role for loading the fact.

prasadns26

 Profile Answers by prasadns26 

• Jul 18th, 2006

 

hi,

usually source records are looked up with the records in the dimension table.DIM tables are called lookup or reference table. all the possible values are stored in DIM table. e.g product, all the existing prod_id will be in DIM table. when data from source is looked up against the dim table, the corresponding keys are sent to the fact table.this is not the fixed rule to be followed, it may vary as per ur requirments and methods u follow.some times only the existance check will be done and the prod_id itself will be sent to the fact.

Anjali

• Jan 31st, 2015

 

Suppose we have two dim Dim_Location and Dim_Customer then how in fact table we can map values of Loc which are corresponding to a customer , if loc has val 1 for Chennai and 2 for Bangalore then how we can show the corresponding loc values for cust ?