How to handle Large dimensions 35M records
Hi all. I have a dimension with 35+ million records as compared to 225 Million in the fact table. I am not sure about the kind of penalty we will have to pay for such a big dimension. Here is summary regarding this dimension. This dimension is derive

Unsure about relationship with Slowly Changing dimensions.
Hi Sorry datawarehouse newbie question! I have many years experience with relational databases but my head is not yet around the dimensional model. I am not sure how to maintain the relationship between Fact and Type 2 Dimension. i.e if a new row is

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

Dynamic dimensions
What is the best way to handle dimensions that change depending on user parameters? For example, lets say you want "Months Since Inception" to be a dimension, because you want to bucket by it (i.e. 0 to 50 Months, 51 to 100 Months, etc.) but

Mini Dimensions
Hi In out data warehouse design (superannuation) we need to cater for Client and Accounts and the relationship between them (a client can have one or more accounts). Some of the client attributes can change so we were thinking or having a client

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

how to update xbmc library?
hi guys, i am using media companion extensively for all my movies an tv shows and everything orks perfectly fine. so great app you built there... i am also using media ompanion for my xbmc client. curently, all my media is stored on a NAS and and clien

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.

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

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.

Slowly Changing Dimensions - Design Review (Need More Clarification)
Hello, Suppose I have following Fact and Dim table CustomerDim CustomerKey CustomerID CustomerNumber CustomerName CreditLimit - Slowly Changing, wants history IsAnnualMember - Slowly Changing, can be different from year to year or

Subsetting date/time Dimensions and Role Playing Date/Time Dimensions
Working at a client site that would like to take a Date dimension using Day as Pk for Day_dim with some day of week, week day, month, year, etc. columns. Suggestion of making more conformed dimensions from Day_dim with Week_Day_dim and Month_day_dim an

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

Hierarchy within single dimension or two dimensions
I am unsure of the best way to model a specific business scenario and was looking for some input. I will explain it in terms of a common example, the Product dimension. Let's say that every "product" is assigned to a specific

Assign default value for a dimension
Hi, We have the following case: For the product code in the source data, lookup the product natural key in the product dimension and assign the surrogate key returned by the lookup to the fact. If the lookup fails, assign the unknown product whose