kvkeee at 18h24
28
Sep
2009
Dimensional table design dilemma, Aditional column or Xref table
Here is my situation.
We have a currency dimension table which stores the ISO currency codes (e.g. USD for US Dollar) and a surrogate key, currency description along with some maintenance columns (insert date, update date etc..).
We are trying to introduce a new source system which doesn't use ISO currency codes. They have their own 3 digit numeric code for every currency. And here is the d
Here is my situation.
We have a currency dimension table which stores the ISO currency codes (e.g. USD for US Dollar) and a surrogate key, currency description along with some maintenance columns (insert date, update date etc..).
We are trying to introduce a new source system which doesn't use ISO currency codes. They have their own 3 digit numeric code for every currency. And here is the d
About
This topic belongs to the forum
Data Warehousing and Business Intelligence based on dimensional modeling and the Kimball Lifecycle.
- Numbers of topics : 1858
- Numbers of messages : 8714
- Numbers of users : 3801
- Numbers of points : 1672
Similar topics
Hi,
I have a scenario where we have dimensional information and the facts in one table rather than a traditional break up into facts and dimensions. What could be the problem i could run into with having all information in one table. Thanks.
Hi
I'm presently modeling a data mart and I would like to use a fact table as a dimension for another fact table. Is it something doable and efficient or is there a better way to do that? if yes should i just create a surrogate key and link both
Appreciate your expert comment on following:
Entities: Quote, Trade, DIRequest, Order User, Customer, Trader, Sales or Marketer and Product
- User is a user who is using the system or interfacing with the system. i.e. requesting quote or placing a
Hi All -
This inquiry could actually be two questions, but the requirement is really presentation of row-wise high volume transactional data in a column-wise (columnar) FACT table.
Here is a sample transactional data set:
Interval Date TimeUni
HI,
I am creating the Property & casualty Insurance DW for Autopolicy
I have PolicyTransactionFact,
DIM_covered_item_vehicle, Policyholder_dim these are FK's in the fact table.
and I created driver dimension table which has driver
Forums from same category
Techy Boards, a growing technology discussion forum! For fans of nintendo, xbox, playstation or anything else!
HmongThoobNtiajTeb. com/
Free forum : Forum IT Teknik Komputer dan Jaringan SMKN 1 SLAWI
Free forum : hi. Free forum : 2709rsgamboa6219. Free forum,
LEGO Island Discussion, modding, news and more!
Search
Informations
2 Replies For the topic :
"Dimensional table design dilemma, Aditional column or Xref table"
This topic has been viewed 1823 times.
Last message :
28/09/2009 at 18h24 by "kvkeee"






