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

Value Banding linked to a calculation
I have an interesting problem - how to hook up value bands to fact rows that require a computation. I have a fact table where the measure I'm interested in is a percentage. In order to cope with roll-ups I am storing the actual and the divisor as

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

How many measures in a fact table is acceptable?
Hi, I would like to find out what is the maximum number of measures allowed in a fact table? Thanks

Monster Dimensions
My customer list is huge (about 70 millionish). We currently have a 60 million row dimension (CUSTOMER) that holds most of our existing customers, and this existing large DIM is currently performing fine for us. Now my clients want to type 2 two

Inventory Snapshot - GMROI Calculation
We are developing a solution for our company. We currently have a sales cube and we are in the process of building an inventory cube. We are having a design problem in that we are not sure if we should include some of the measures which currently exist in

Time Dimension vs Measures in Minutes
Hi All, I would like to design the time in a multidimensional model. The classic calendar date dimension (day, week, month, year) should be applied here. Besides that, I have a fine grain: the minute. More specifically, let's suppose I have 10.000

SET2/Q.1 a. What is demand forecasting? Explain the basic approach to forecasting demand.
Q.1 a. What is demand forecasting? Explain the basic approach to forecasting demand. (8 marks) b. Define supply chain management. (2 marks)

ETL approach for replacing multiple dates in one row.
We have a Fact table that stores several key dates in the life cycle of a customer. Each of these dates is supposed to be a surrogate key pointing to the date dimension. My questions pertains to efficiently replacing these dates with surrogate keys in the

Dynamic dimensions
What is the best way to handle dimensions that change depending on user parameters? For example, lets say you want "Months Since Inception" to be a dimension, because you want to bucket by it (i.e. 0 to 50 Months, 51 to 100 Months, etc.) but

internationalist approach to resolve all outstanding issues between Iraq and Kuwait
Bwalun: internationalist approach to resolve all outstanding issues between Iraq and Kuwait Topic 6 has been read once 31/01/2011 Paris will seek to re-integration of Baghdad, the international community Baghdad, Omar Abdel-Latif Said French

Mini Dimensions
Hi In out data warehouse design (superannuation) we need to cater for Client and Accounts and the relationship between them (a client can have one or more accounts). Some of the client attributes can change so we were thinking or having a client

Flat File Importing via SSIS - Best approach?
My company is frequently faced with the need to import and profile flat files submitted by various prospects and customers. These customers rarely provide us with a format file and when they do it is rarely accurate. Importing CSV files is slightly easier

Derived Fact table with additional measures / foreign keys ... ?
Hi, Let's say we have a fact table: FactReceipt which contains all our receipting transactions that occur during the month, we may have 5 receipts of different types during one month for one contract. Now let's say we build another fact table that

time relatives - YTD, MTD, QTD the best approach
What are the various design options for calculating fact by YTD,MTD, QTD for multiple different calendars?