Laszlo at 02h18
09
Dec
2010
Fact table design: Sales Transaction with multiple Discount rows
Hi,
I am designing a Sales DW where we can have multiple discounts on a given transaction line.
I created a SalesTransaction (ST) fact table and a SalesDiscount (SD) fact table.
In the current design the ST table has its own key that is a bigint (ST.ST_KEY). I am linking the two fact tables together using ST.ST_KEY = SD.ST_KEY.
I am open for alternatives as I ha
Hi,
I am designing a Sales DW where we can have multiple discounts on a given transaction line.
I created a SalesTransaction (ST) fact table and a SalesDiscount (SD) fact table.
In the current design the ST table has its own key that is a bigint (ST.ST_KEY). I am linking the two fact tables together using ST.ST_KEY = SD.ST_KEY.
I am open for alternatives as I ha
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 am faced with a problem designing a transaction fact in an investment firm. each transaction represents a trade the traders put in (buy,sale etc).
The problem I am facing is: the metrics of a transaction change from one day to another day so 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
I've been reading more and more Kimball literature and I'd like clarification on something.
Transaction Fact Tables are rarely revisited because they do not need to be updated, deleted, etc but typically only appended to.
He goes on to describe
Hello,
I have a dimension used to store several types of 'bands' like monthly income bands, available income bands, risk bands, settlement bands etc. If I leave out all the lineage columns this is what the dimension looks like:
DimBandID BandType
Hi,
I was wondering if there is anything wrong with having a factless sales table?
Basically all I am required to do is to count up the total number of sales that occurred each month grouped by product type. So basically all I have in my fact table
Forums from same category
HmongThoobNtiajTeb. com/
Free forum : hi. Free forum : 2709rsgamboa6219. Free forum,
Free forum : Forum IT Teknik Komputer dan Jaringan SMKN 1 SLAWI
LEGO Island Discussion, modding, news and more!
Techy Boards, a growing technology discussion forum! For fans of nintendo, xbox, playstation or anything else!
Search
Informations
2 Replies For the topic :
"Fact table design: Sales Transaction with multiple Discount rows"
This topic has been viewed 1643 times.
Last message :
09/12/2010 at 02h18 by "Laszlo"






