Snowflaking Dimensions

Specify acceptable Snowflaking scenarios

Can someone please specify acceptable snowflaking scenarios. - Thanks in advance bi_at_nj

Dimensions Directly Tied to Facts vs. Snowflaking

Hi all, Thanks in advance for your input on this. We are in the midst of a building out a portion of our data warehouse. The example here has to do with insurance data. Hopefully the discussion can be abstracted to a more generic modeling level. We

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 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

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

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

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

A fact table surrounded by a lot of references tables

I am reviewing a design which is about to be implemented after build. There is a fact table with 17(!!) foreign keys. 14 of these keys are two-letter codes pointing to reference-tables (as we call them). A reference table consist of codes with

Linking or Merging Similar dimensions from Different Source Systems

We've got a situation with the DW we're building where we have 2 seperate systems that we are wanting to bring the data together for cross analysis 1) The first system is the main operational system ie a contact management application that records

Dimensions - To Create Based on Type or Role ?

I'm trying to lay down some guidelines for creating new dimensions in an existing shop. I have a mix of dimensions that are type-based and role-based. Type-based are those created because an entity (think Party) has many types (individual,