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

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

Multi valued dimension attributes, weighting factor and cognos
Hi, we have several attributes in our product and customer dimension which might by multi valued. We modelled these as multi valued dimension attributes using bridge tables and weighting factors therein. Can anybody reference a best practice

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

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

What to do when the weighting factor of a bridge table no longer seems relevant?
I have a fact table that has healthcare claims data. Since a given claim can have multiple diagnoses, I'll use a bridge table that links a bridgekey from the fact table to the bridge table. The bridge table will also have a diagnosiskey that ultimately

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

multiple hierarchy : single dimension vs multiple
Hi Need to analysis sale revenue by store. We have two separate hierarchy for geographic location 1. Country / County / Council / Store name 2. Country / Region / Area / Store name Need valuable suggestion for how to design dimension for above to

Multivalued Dimension or Multiple facts w/conformed dimensions
I am trying to model for insurance industry, with data as follows: We have data at different levels: Policy level with related facts. ((Premium , face amount, mode etc) Policy Fund level (combination with related fact values.) Policy Rider level

Multiple facts in a fact table
One proposed model for our business (wholesale/retail) sales fact is to have every register ring in one fact. This causes refunds, voids, coupons and other 'facts' to be stored in a single fact entity. There is a column type dimension that then tells us

Date Dimensions - Muliple Calendars
Hi, We have an interesting challenge with our Date dimension. We need to carry multiple calendars - one per country, and one for the Group. When loading the FACT, we create a record per invoice for the country and a record for the group calendars. Thi

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

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

Employee With Multiple Jobs
Hello; I am developing an Employee Transaction Dimension such as that seen in Figure 8.2 of the "The Data Warehouse Toolkit". In my case, an employee may have multiple jobs. Some of the attributes found in the Employee Transaction Dimension

1 Dimension used multiple times in 1 fact table?
Hello, I have a dimension used to store several types of 'bands' like monthly income bands, available income bands, risk bands, settlement bands etc. If I leave out all the lineage columns this is what the dimension looks like: DimBandID BandType