Modelling KPI values

Textual values in dimension tables

With much interest I am reading "The Data Warehouse Toolkit", and I stumble upon a design thing that I have done differently in my Data Warehouse design (this is described in the book on page 42). It describes about the dimension table that it

Null values in facts, yes or no?

Dear all, I'm wondering if anyone could help me out with the following (simplified) case. This is for my Business Intelligence study on a Dutch university where we do a project to apply BI to the student information systems, especially their results an

NULL Values in Fact Table

In an Accumulating Snapshot that has multiple dates, where we are revisiting the fact rows as additional events occur, should the foreign keys to the date dimension for dates that have not yet occurred be set to NULL or should they point to a

Measures as Dimensions: Banding Approach Help

I have a standard fact table with a number measures; several of which are in the form of time (e.g., minutes) and others in the form of integers. The fact table and related dimensions are exposed to users via BusinessObjects XI v2 Web Intelligence. One of

null values best practice digest

Hi all, i read all the post and design tips about null values management. Can you tell m if the following statements are right or wrong for you : Dimension attributes null values management : For string dimension attributes, use : "Not

read values from runScript method

hi, my javascript function call which is defined in browser is not working with geteval so i am using runScript, I am able to get the values in alert but don't how to read these values? selenium.runScript("alert(getBoundaries());"); PLeas

Android Sensor API

Hi, Android Sensor API Sensor support in Android is fairly simple yet versatile. It is handled via the SensorManager which is provided from your app context via getSystemService(). Once you have the sensor manager, you have to register to get its

Some Practical Challenges

Hi All I am facing some challenges in my dimensional modeling and most of these are covered in many books too.But i have practical limitation for that 1st Challenge :Unbalanced Hierarchy In one of the dimension we are tracking employees and their

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

Multi valued dimension attributes, weighting factor and cognos

Hi, we have several attributes in our product and customer dimension which might by multi valued. We modelled these as multi valued dimension attributes using bridge tables and weighting factors therein. Can anybody reference a best practice

"Previous" attributes

I am working on a HR Enterprise datawarehouse. I have a requirement for a number of "previous" attributes. For example, an employee's previous business unit, supervisor, last name. Business Unit, Manager already have their own Type 2 SCD

Data mart design

Lets say I need to model Frauds. There is 2 departments handle different Frauds say (Contract and Health care). I am going to model this in MD (fact, dimension). Now should I just create one Fact table(Business Process) and use say Fraud type (Contract,

DatawareHouse modeling (factless table)

Hi everyone ! (To begin, I want to apologize for the bad english i'm gone use cause im french canadian) system i'm using : Sql Server 2005 Ent SSAS 2005 (For cube) SSIS 2005 (For ETL) I'm in the process of building a datawarehouse for the