Disadvantage of Fact table with 44 columns

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

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

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

Guidelines for FACT Table Design for High-Transaction Volume and High # of Measures ...

Hi All - This inquiry could actually be two questions, but the requirement is really presentation of row-wise high volume transactional data in a column-wise (columnar) FACT table. Here is a sample transactional data set: Interval Date TimeUni

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

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

Converting Columns into Rows.

I have a requirement where I need to convert rows in columns. The data is quite huge there would be around 200 million records. The sample table contains only data for five months but in actual 12 months of data come in a single row and number of columns

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

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

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

Random Facts October

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