Help in declaring grain and identifying dimensions
Requirements: 3 Reports ----------------------- Source Systems: 3 Project DBs 1st Report : Portfolio Summary Details The project monthly details report will display project information i.e. summary actual costs from the Vendor History file

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 facts in a fact table
One proposed model for our business (wholesale/retail) sales fact is to have every register ring in one fact. This causes refunds, voids, coupons and other 'facts' to be stored in a single fact entity. There is a column type dimension that then tells us

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

Conformed Dimension for Transaction Fact and Accumulating Snapshot Fact Table
I'm working on a new warehouse application for reporting against our IT Project database. I want to create both a transaction fact table and an accumulating snapshot fact table. The project database (source) consists of multiple normalized tables to

Conformed Dimension Processing Multiple Data Marts
Rookie question. We have 8 conformed dimensions and we are on our 4th data mart using some of these 8 conformed dimensions. We build the conformed dimensions once every night because the client wants to complete full refresh only. The client has

Dimensions in fact table
Hello, I'm working definining a dimensional model in a bank. We have Teradata as DB and MicroStrategy as BI tool. We have many fact tables and most of the fact table lowest level is the "Contract" dimension. We have many other dimensions that

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

1 Dimension used multiple times in 1 fact table?
Hello, I have a dimension used to store several types of 'bands' like monthly income bands, available income bands, risk bands, settlement bands etc. If I leave out all the lineage columns this is what the dimension looks like: DimBandID BandType

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

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

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

Multi level grainulity in Fact table
Hi , I have strange scenario . The fact table needs to be loaded in different Multi Level Grainluity ,this typical scenario was handled in ETL with complex coding. Advantages of so, 1) The report was directly taken from single table and had no

Employee With Multiple Jobs
Hello; I am developing an Employee Transaction Dimension such as that seen in Figure 8.2 of the "The Data Warehouse Toolkit". In my case, an employee may have multiple jobs. Some of the attributes found in the Employee Transaction Dimension

Multivalued Dimension or Multiple facts w/conformed dimensions
I am trying to model for insurance industry, with data as follows: We have data at different levels: Policy level with related facts. ((Premium , face amount, mode etc) Policy Fund level (combination with related fact values.) Policy Rider level