Sparse dimensions, how to handle?

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

How do you handle weighting when you have multiple mulitvalued dimensions?

I've been reading The Data Warehouse Toolkit (2 ed.) and I can't seem to find a section that discusses how to handle weighting when more than one multivalued dimension is included in the design. I work with healthcare claims; we're in the process of

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

Modeling multiple multivalued dimensions and other design questions

Hello, all. This is my first time working on a dimensional model and I have some questions regarding multivalue dimensions. I am modeling our Remedy trouble ticket process and was settling on the grain being each individual ticket. The problems come in

Degenerate Dimensions

Hi there, I have come across a situation where my Fact table contains a degenerate 'Claim Number' column. This is fine, but I have discovered that some of the incoming data to populate my fact table do not have a claim number. How should I handle this

How to handle a Flame War situation.

Flame wars have been popping up a few times, while rare, if it does happen, this will teach you what and what not to do when in/discovering a Flame War. What to do on Pivetworld: 1. Try not to get involved. 2. Always log out if you sense a Flame

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

Determining a users dynamic id

Hi all I've read quite a few forum topics and I have always managed to stumble across something that will get my problem solved. But this time I'm going to register and sign in and write up a query. I'm a bit of a newbie and to testing in general,

How to handle a Type I or II dimension with a snowflaked customer sub dimension (kimball book page 337, 338)

Hello, Within Ralph his new book he describes recommanded situations for snowflaking a dimension. His example is a large customer (visitor) dimension. (page 337, 338 and figure 10-6). I find the artical good, but there is missing one part of 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

How to handle a overly-"helpful" acquaintance

A customer where I work noticed the other day that my eye was drooping and I was in obvious distress. When he asked I simply said "I suffer from chronic migraines". He is invading my life. He walked into my office the other day, started

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

Date Dimension

Hi All, I understood Kimball way of implementation Date Dimension table. In a way, the lowest granularity date represent each record, with the following month, quarter and year attribute. However, what happen if the lowest grain of certain fact are at