Schema Roadblock: Dimension vs Fact [Dimensions w/FKs to other Dime...

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.

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.

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

Cube Processing for Dimension Schema changes

Hi, I had a general question about how cube processing works. If my dimension schema changes (an addition of a property), will I have to do a full reprocess of all cube partitions for which that dimension was member of? Or do I only need to

Supplier Dimension to include Customers & Employees

We are in the process of finalising Dimensions /Facts to be used in Datawarehouse. Already finalised separate dimensions (eg Customer,Supplier,Employee) to handle requirements of Sales,Purchace and Human resourses. During designing Accounts Payable Fact

Flexiblity To Add Attributes To A Dimension And Not Process The Whole Cube/s

Hello, We are in the process of designing a DW for Games and have run into a business problem : Business users want to add attributes to a dimension and decide its level in the hierarchy on the fly. The new attributes should be availabe in reports

How to manage Conformed dimensions

Hi, If I'm implementing data mart by data mart, I build a dimension for the first data mart. After a few months, I realize I can use that dimension for the second data mart as a conformed dimension. But it needs additional columns. How do you manage this

Reasons to use a 3NF design over a Dimensional Model design for an EDW - Discussion

I've been dimensional modelling for well over 10 years, and strongly held the opinon that only a dimensional model would work for an EDW, however i'm now begining to think that there are certain requirements that lead to a 3NF design for an 'Enterprise

Data Vault v's Dimensional Model

Seems to be a lot of interest over at LinkedIn around the DataVault model. I wondered what the thoughts were about it. When would you use it v's a Dimensional Model or even a 3NF for a data warehouse. more info here:

Bridge Table and Customer Hierarchy

Does anyone know of a good detailed reference that discusses populating and maintaining customer hierarchy type bridge tables? The only decent resource I've found is the "The Data Warehouse ETL Tool Kit", but it only briefly shows an example on

Schema Roadblock: Dimension vs Fact [Dimensions w/FKs to other Dimensions?]