Facts at different levels of hierarchy
Let's say I have an empoyee dimension consisting of the usual attributes describing a person, but also these two: Department and Company. Let's also say I have budget numbers for the three levels (Employee, Department, and Company). I would think tha

Conformance of Dimension for facts aggregated at different levels
I am a newbie to Data Modeling. I am modeling a warehouse for Global reporting solution for a business operating in 3 countries. 2 business processes involved are "Sales" and "shipment Expenses" The input is sumarized excel files

Facts at different levels.
Hi Everyone, The data I have has no perticular grain statement on which I can base my model.. Can someone suggest a better design for this scenario, Simplified version is,... I have 2 dimensions 1) Property.. Heirarchy is Site -> Building

Dimension Hierarchy - Facts by various levels
Hello, I am working on a new project (with Oracle OBIEE) where most data needs to be seen by a terminal(game or cahsier). The terminals are located in different venues in various cities and states. Some terminals may just be at a city or a state level

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

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

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

Migraine and testosterone levels
I have heard that there may be a link between men who suffer migraines and having a low testosterone level. There are a number of websites that back this up, but I am sceptical of anything I read online. There was a proper study done in 2005, but it only

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,

Facts or Dimension Attributes?
My company is currently building a data warehouse and I have a design issue that I am not sure how to address. In general, our business is selling an asset, such as the stock of a corporation, with a certain number of shares and a value. The value of th

your interesting facts
so basically you put interesting facts about yourself such as something really good or really bad you have done,something really good or really bad that has happened to you, or just something you want to share about yourself.you can also put any

Non-numeric Facts
My customers are challenging me..... They tell me that my reporting models are not flexible enough. I agree, but I am not sure how to approach this issue and give them what they need in a simple way. My products today offers 2 types of reporting today:

Have You Scrutinized The Facts About Juicing, Healthy Diet, Juicing For Better Health
By David Wellsford We are all very aware today the benefits of good nutrition, and the vitamins, and minerals that are necessary for our health. What do we know about juicing, healthy diet, juicing for better health? What does juicing mean? Making

Dimensions Directly Tied to Facts vs. Snowflaking
Hi all, Thanks in advance for your input on this. We are in the midst of a building out a portion of our data warehouse. The example here has to do with insurance data. Hopefully the discussion can be abstracted to a more generic modeling level. We

2 facts or 1 fact - Revenue and time billed
Hi, I'm trying to get my head round how to model my fact tables. I work for a consultancy and I'm building a warehouse to track the revenue and chargeable hours worked by our consultants. I already have one fact table (FACT_TIME_BILLED) whose grain