Schema Roadblock: Dimension vs Fact [Dimensions w/FKs to other Dimensions?]
Hello, I'm new to DM, I've picked up Kimball's DW Toolkit and DW ETL Toolkit - both great books. I'm designing a simple datawarehouse for eduction (K-12) and ran into a modeling question. I'm designing the portion pertaining to [homework]

how many dimensions is too many
If I have a fact table with too many dimensions --- over 30, does that mean I've created dimensions when they could have been attributes to another dimension table or possibly that I am trying to capture too many business processes within one fact table.

Sparse dimensions, how to handle?
I've purchased the book "The Microsoft Data Warehouse Toolkit" and have reviewed it in order to build out a data warehouse solution I am currently designing. I am stuck in a spot that I don't seem to find any examples of , or am not abl

Monster Dimensions
My customer list is huge (about 70 millionish). We currently have a 60 million row dimension (CUSTOMER) that holds most of our existing customers, and this existing large DIM is currently performing fine for us. Now my clients want to type 2 two

Snapshot Dimension & Fact tables
We are currently designing a logical multidimensional model from an OLTP tables.Dimension tables have monthly snapshot because some of or all the attributes might change on monthly basis.The same situation for the fact table has monthly snapshot. I kno

Preserving prior history for late arriving dimensions
Can't find much about this topic anywhere else so hopefully someone can help me. Our warehouse has late arriving dimensions for an Employee. Their department changes, for example, can be backdated in the systems and so we have to account for this and

Dates in many dimensions
Hello, I am new to DW. Currently, I am working on a Human Resource database. There are many tables in the source systems which stores dates e.g. dates about contract start, finish, Vacations of an employee, temporary service suspension and many more.

SCD Type 2 dimension and fact table being the same table
I am designing a dimensional model for employee data in a data warehouse. Right now I only register the basic information about the employee, like job title, department, language, FTE, etc. I have chosen to use an SCD Type 2 dimension since I want to keep

Advice on relationships between Type 2 SCDs ?
Hi All, I am constructing a new warehouse schema containing a number of dimensions which need to be modeled as type 2 SCDs. This is all fine and I have surrogate IDs which are being used as the FK in the facts. The challenge I have is that a number of

Joining Type II Dimension Hierarchy directly to Fact versus through a Dimension table
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

Dimensions in fact table
Hello, I'm working definining a dimensional model in a bank. We have Teradata as DB and MicroStrategy as BI tool. We have many fact tables and most of the fact table lowest level is the "Contract" dimension. We have many other dimensions that

Best Praticte for inserting fact and linking to dimensions
Hi all, is it allowed to have null values in fact table for some dimensions foreign keys ? Exemple : DateDimFk DimFk1 DimFk2 50 (coming from business system 1) DateDimFk null DimFk2 50 (coming from business system 2) or do i have to create a

Rapidly changing Monster dimension...
Hi Everyone, I have a list of more than 300 attributes, which are actually part of the fact table….(basically ..these values changes for each transaction level record in fact but belongs to a single dimension). that lot contains more than a 100 date

Same attribute in multiple dimensions or Create new dimension?
Hi all - I'm struggling with this concept. I have 2 dimensions: Customer and Products. Both share a common single attribute that I'll just call "Owner" for now. If a customer purchased a product, the owner would be the same for both. I

fact table as a dimension
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