NULL Values in Fact Table

Null values in facts, yes or no?

Dear all, I'm wondering if anyone could help me out with the following (simplified) case. This is for my Business Intelligence study on a Dutch university where we do a project to apply BI to the student information systems, especially their results an

Loading Fact table

Hi, I have following tables FACT, A_DIM, B_DIM. How do I update relationship between a_key and b_key in the FACT table when new record arrives in TYPE2 a_dim dimension? Below is simple create scrip to illustrate what I mean. create table fact (a_key

How to manage nulls in Fact talble

Hello, I am new with data warehousing. I need some help with following questions 1. should the nulls be left as nulls in fact table or should they be replaced with some number that might never be used like -7 or -1. If they should be replced with -1/-

Fact table with non-numeric measure

I have a transactional fact table containing results of inspections. The results are non-numeric, but do represent a measurement, that is inspection result (like "pass", "fail", "pass with infraction", "failure with

null values best practice digest

Hi all, i read all the post and design tips about null values management. Can you tell m if the following statements are right or wrong for you : Dimension attributes null values management : For string dimension attributes, use : "Not

Transactional detail fact table w/complimentary snapshot table. How do the two play together?

Take a detail daily banking transaction table with standard credit and debit level transactions. I want to build the accompanying snapshot that would present the higher level rollups of these lower transactions: There are about 250 daily transaction

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

Montly Snapshot views with transactional Fact table w/SCD2

I am a new at working with Dimensional Database design. I am struggling with something that probley is real easy to do, but just can't find documentation that will explain it. I want to create a monthly snapshot view of my transactional Fact table with

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

Questionnaire for medical record entries

Good afternoon, I am currently working on a data warehouse in the health care sector and I currently facing this problem: The aim of this warehouse is to have an overview of a cancer therapy. So, I have created the following fact table

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

Bridge tables versus massive junk dimensions

I am designing a star schema to store information on hospital stays. This is my first real star schema and things are off to a good start. My fact table is hospital stays. I have a diagnosis dimension. There are multiple diagnoses per stay. Costs are

Dimension with two hierarchies

I need to design a dimension with two hierarchies 1. Location -> Building -> Room -> Cabin 2. Location ->Building I need the hierarchy 1 to be referenced in one FACT table and hierarchy 2 in other FACT. But my ETL tool allows only the dimension ke