Overlapping Dates in a dimension

Overlapping facts

Hi, I have a fact table containing diagnoses. So far, fine. I have been given a new dataset with more diagnoses, (from when our patients visited other hospitals) and some of these new records refer to diagnoses that I already have, and some do not.

Fiscal Dim and Snapshot Dates for Budgets

Hi everyone, I have a couple of questions regarding fiscal dates and snapshot dates/data: 1. How would someone model a "fiscal" dim when a date maps to two fiscal months? e.g. Fiscal Year 2010 Fiscal Month 12 Fiscal Month Date

Dealing with empty/missing dates in dimensions

I'd like to know other people's opinions on how to deal with missing dates in dimensions, which is a situation that happens quite frequently (for example, think of birth date in a customer dimension). We all know that attributes in dimensions should not

Null value for dates

All of my dimension tables have a value -1 that means there was no match to then dimension table. I try to put in some value such as "Unknown" or "Not available". Any suggestions for the -1 row in a Date dimension? Should I use some future date suc

Degenerate dimension & accumulating fact

I am currently looking at the design of an accumulating fact table that has order number as a degenerate dimension (the snapshot is one row per order). There are a few additional fields that apply to the order, that are also being carried as additional

Fact table with multiple date ?

Hi, I am modling a fact table for prisoners inscription in order to track historical changes. An admission is the hole stay comprise of one or many inscriptions usually separated by transferts between institutions. In the transactionnal system, it

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

Combination of SCD2, partial snowflake, Effective and end dates in fact table

We are creating dataware housing for multitanant based systems for HR module. Requirement ?Able to report on historical data for any given data time. Active employees headcount till given date. (as of that day) Onhire and termination based on perticula

Audit Dimension Help

Hello all. I'm at the stage now where im building the audit dimension for my warehouse. I am having a little trouble figuring out a few things though. How do you aggregate the data from the error event fact table into the audit dimension? Some records

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

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

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

Regarding Factless Fact Tables

Some time ago I was asked to build the BI platform for a road safety organization. The warehouse was built of three primary fact tables, each with a collection of associated dimensions. I am now trying to branch out into ETL and Warehouse design, and from