Modelling question - Multiple fact tables with one to many relation...

Multiple Fact Tables vs. Consolidated Fact Table

I am trying to put together the bus matrix (to identify the facts tables) for a government correctional agency and am debating between multiple facts for each event in the life cycle of an offender vs. fewer fact tables. I wanted to avoid joining multiple

Multiple measures in a fact table- modelling question

Hi all, First, sorry for what may be the super easy question for you... There are around 100 different metrics with the same grain to be analyzed against the same set of dimensions. The initial idea was to build one big table ~100columns wide with a

Using a dimension in multiple fact tables with different grain and support SCD

Hello users, i've a question about using a dimension in fact tables with different granularity and at the same time retain support for SCD. My scenario: I have one Dimension called Apartment. This Dimension cosists of the following related

Multiple fact tables

I have forecast and actuals information about budget. They would all share most of the dimensions and would have the same fact attributes. What are the benefits/ downsides of having a fact table for forecast, and another fact table for actuals vs. having

Multiple Many-To-Many relationships

I've read quite a bit on dimensional modeling but this would be my first go in reality. Any help would be greatly appreicated. Here's what I've got... An existing subset of our DW would be: Fact_tx Dim_Customer Dim_Product One of our source

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

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

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

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

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

Multiple Memberships IP Warning system.

Most sites have a ip scanner system on them that will flag up the members that have the same ip address and tell the admin's the ip and the names of the users. Right now the only way to see the ip and the ones that have more then one account is when th

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

Multiple Theme/Skin Selection 4 Members

There are some forums that allow you to use more then one template, the user can choose which look they want, we should do that with our sites!

Modelling question - Multiple fact tables with one to many relationships and querying from many fact tables