Facts with different grain from different sources but related
Hi, I have a situation which I am trying to resolve but not able to Technologies Using : SQL Server and Analytics Services (SSAS) Background I have a flat file which is from the enterprise peoplesoft system and has the followings GL Account,

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

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

Multiple one to many facts
Trying to figure out how to model this with multiple one to many facts. I'm new to modeling so bear with me if this is simple. I think a picture speaks a thousand words so here is this: There's a few dimensions as well but those are easy

Textual Facts in the fact table
Its a new financial 'capital markets' dimensional reporting model (for IPO - raise money for an issuer by issuing new equity common stock securities) that's in design stage. There are some textual attributes of the grain of several fact tables for which

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

Modeling for Service related facts and dimension (for Tour Operating Company)
I am currently doing a dimensional model design for a Tour operating company. Their business is like selling hotels rooms, flights, and excursion to customers. All these are called SERVICES. Now I am designing dimension and fact table to hold bookings

Mixed grain issues
I am in the process of modelling a typical sales invoice. The header contains the usual suspects...Invoice Date, Customer Number, Tax Amount, Total Amount. The detail is also unremarkable...Product Number, Qty Ordered, Qty Shipped, Total Amount. In

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

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

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

data model for 2 fact tables (Header / Detail scenario)
Hello, I want to verify that I have this data model correct to present as the high level design. Requirement: 2 facts to be available in one cube. Facts must be separate physically (regulatory) and it is a header / detail scenario so we do not want

Question on symmetry in Star schema
Hi I read Kimball's Data warehouse toolkit and I came across a point that one of the advantages of having star schema is - BI / reporting tools in the market can leverage the symmetrical nature of the star schema. From what I know and I could

Duplicating a field in more than one fact table.
Question about dimensional modeling. Scenario: I have a dimension called: 1. Dim_Application And two fact tables: 1. Fact_ApplicationStatus 2. Fact_ApplicationConsolidation Now the Dim_Application consists all the applications

multiple 'fact' tables - daily detail and monthly allocations
I am sure this has been asked but I could not find a direct answer. We have an EDW with a transaction level fact table including pertinent financial detail. For the purposes of this question there are multiple transactions per client, and multiple clients