NULLs in source lead to duplicates in Fact table

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

NULL Values in Fact Table

In an Accumulating Snapshot that has multiple dates, where we are revisiting the fact rows as additional events occur, should the foreign keys to the date dimension for dates that have not yet occurred be set to NULL or should they point to a

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

Source for Accumulating Snapshot Fact table

I have a question about accumulating snapshots and I was hoping someone could shed some light on the subject. Does Kimball give any guidance anywhere (books, online, etc.) as to whether one should build the supporting transactional fact tables that

One Fact table having records at different granularity level

Hello, My question is just validation for an approach that we followed for one of our client requirements. Based on the requirement the FACT table should be constrcuted by the records from 2 Source table A and B. The structure of the table is as

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

China to cut lead-acid battery recyclers

(Reuters) - China will cut the number of firms it allows to recycle lead-acid batteries for refined lead production, a top industry official said on Sunday. Industry sources estimate China will only allow around 20 battery recyclers to operate in the

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

new odroid project kick-off for developers.

Hardkernel team appreciate all your comments in this community. This hardware specification is generated by ideas from this community members. ODROID-7 has lots of improved features such as built-in camera, 11n-WiFi and internal GPS. Enjoy

Random Facts October

They grow up so fast! RF: The staff is organising a birthday party for the forum, but don't tell anyone!

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