A fact table surrounded by a lot of references tables

Cost plans for projects - One fact table or several fact tables?

Hi, I'm currently struggling with my Dimensional Model. It is about projects with their related cost plans. Every project starts with an initial cost plan (called WIPL), the project is saved as version 0 and the WIPL attribute and the ACTUAL attribute i

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

DATE OR DATE KEYS IN FACT TABLES

I've read different opinions about the usage of dates in fact tables. If a date is NEVER used to filter and only reported, what is the purpose of adding it as a date key instead of a plain date type? Aren't we wasting the resources to get to the date

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

Does it belong in the stage tables or fact tables?

If I have a fact table with a "counter" fact, for example a customer places an order, but then goes back and changes parts of that order any number of times, I want to store how many times the customer changed his/her order. The grain of the

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

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

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

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

Dimensional Model Vs Views as Structure for BOBJ Universe

I have a fairly complex data mart (multiple fact tables: 5 at the moment and several more coming; 4 shared dimensions across the 5 facts, 26 total dimensions and several bridge tables). I used standard best practices for building the Business Objects

100 reasons why Madeleine was not abducted

http://blogs.news.sky.com/discussions/show.html?plckForumPage=ForumDiscussion&plckDiscussionId=Cat:746f9309-1bb1-4b07-ad11-647f5ba16800Forum:4237bf3e-0948-444d-a452-46289a2fd1f7Discussion:53085ce6-d0e9-4517-9607-a2eb2b4b9b84 class=Discussion_PostTi

Random Facts October

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

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