Monster dimension, joining fact tables

dwfavor at 17h02
01
Feb
2011
Monster dimension, joining fact tables

I am newbie to the DW. We have document processing OLTP system with the following tables

Document table (partitioned table, approx. 1 billion rows)
DocId -PK
Title
DocDate
… 10 other columns

Users table
UserId -PK
UserName
.. 3 other columns

DocumentUsers (joining Document and Users table) (partitioned table, about 10x Document rows
About
This topic belongs to the forum
  • Data Warehousing and Business Intelligence based on dimensional modeling and the Kimball Lifecycle.

  • Numbers of topics : 1842
  • Numbers of messages : 8656
  • Numbers of users : 3787
  • Numbers of points : 1497
Similar topics
I am having trouble joining two fact tables. I have read the different topics and see that the bridge table would be my logical option. The subject I have is Orders. I can place an Order which may contain many items...as well as, the items can be a par
Is it appropriate to relate different grain dimension tables (aggregate dimensions) with the same transactional fact table?
The title question is kind of rhetorical because I didn't actually think it was a common practice but I was hoping someone could offer an alternative . Let's say I have a fact_service_provided table where each row describes a service that the business
I have a order fact table. I have a call fact table. For each order, there is a call associated with it. Would I have the call id on the order fact and to join the 2 facts?
Given I have 3 tables, Workforce Event Fact, Department Dimension (Type II SCD), and a Department Hierarchy (Type II SCD), and assuming the DEPTIDs in the Department Dimension table are reflected in a BASEDEPTID field in the Dept Dimension hierarchy table
Forums from same category
See also
more_less
Informations

6 Replies For the topic :
"Monster dimension, joining fact tables"

This topic has been viewed 1404 times.

Last message :
01/02/2011 at 17h02 by "dwfavor"