data model for 2 fact tables (Header / Detail scenario)

Fact dimensionality

I often run into the situation the we have several fact tables with different grains, but are related through a single ID at the transaction level. Typically the dimensionality is the same, but the related information doesn't exist in the source

Monster dimension, joining fact tables

I am newbie to the DW. We have document processing OLTP system with the following tables Document table (partitioned table, approx. 1 billion rows) DocId -PK Title DocDate 10 other columns Users table UserId -PK UserName .. 3 other

Header Level Dimension for a Fact Table

Hello, This is an EDW solution for an insurance company that I've been designing. I have FactMonthEndTrans (This is per policy per coverage for every month) =============== - MonthEndSnapshotDateKey - PolicyKey - CoverageKey -

Fact Table Grain at a Sub-Atomic Level

I'm thumbing through the Design Tips and would love to find some thought given to the statement made in The Data Warehouse Toolkit: The Complete Guide to Dimensional Modeling (pg 34): "Preferably you should develop dimensional models for the most

Building aggregate fact tables from staging

Hi, Is it acceptable to create an aggregate fact table from the staging tables after you have cleaned out the data in staging? I know usually you're supposed to create aggregate fact tables from the fact/dimension tables, however can it be done straigh

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

how to model an event log

I am trying to model the following event data: Field1 = event date, field2 = event code, field3 = location code, field4 = customer_id, fields5 to 8 are event code specific, ie.

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

Fed Tells U.S. Banks to Test Capital Against Recession Scenario

By Craig Torres and Hugh Son Feb. 17 (Bloomberg) -- The Federal Reserve ordered the 19 largest U.S. banks to test their capital levels against a scenario of renewed recession with unemployment rising above 11 percent, said two people with knowledge

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

Reasons to use a 3NF design over a Dimensional Model design for an EDW - Discussion

I've been dimensional modelling for well over 10 years, and strongly held the opinon that only a dimensional model would work for an EDW, however i'm now begining to think that there are certain requirements that lead to a 3NF design for an 'Enterprise

Banner/LOGO/Header [REQUEST]

Nature of the creation : Banner/LOGO/Header Creation size (in pixels) : H:672 W:174 pixels With or without animation : NO Background color : Try to make it match my FORUM please! Picture(s) link(s) : 3D COMPUTER/LEPTOP Text to insert : IT Fun PK The

Data Vault v's Dimensional Model

Seems to be a lot of interest over at LinkedIn around the DataVault model. I wondered what the thoughts were about it. When would you use it v's a Dimensional Model or even a 3NF for a data warehouse. more info here: