Multivalue attributes
I am working on a model for use by the fund raising unit of our university. They want to be able to do some CRM type reporting on our alumni / donor data. In creating a constituent dimension I have found that there are a large number of attributes tha

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

User Defined Dimension Attributes
I have a business requirement that is somewhat stretching my modelling skills. The application is a highly sensitive one so I’ll describe the problem using a Sales Datamart template. There are 7 plus fact tables, 1 is updated monthly, the rest

Conformed Dimension Partial Set of Attributes
Hi Just looking for some confirmation that a dimension with partial attributes might still be considered conformed. For eample A dimension of batch ProdBatch PK BatchID Batch Name Product ID Product Name ... at an invoice Fact table

attributes depending on more than 1 dimension (2 dimensions)
suppose you have - a discount code attribute - a status attribute which depend on the combination of the dimension customer & the dimension product. You want to be able to relate these attributes to a fact table invoice details. What are the

Multi-valued dimension with distinct attributes
In the health care data analysis DW, the grain of one of my fact tables is the episode of care. How can I include procedure codes performed on an episode ? if I create a multi-valued dimension for it and used bridge tables to model this, it will end up

Different dimensional attributes in different 'dimension-like' source tables
This is a simplified version of the modeling issue that I am facing. Looking to the experts for advice. The product dimension has three attributes- sku, color and weight. Each attribute is stored in its own table with its own transaction date and

Modeling multiple multivalued dimensions and other design questions
Hello, all. This is my first time working on a dimensional model and I have some questions regarding multivalue dimensions. I am modeling our Remedy trouble ticket process and was settling on the grain being each individual ticket. The problems come in

Adding new attributes to a dimension
We're an Oracle 10g warehouse site and still get nervous when adding new attributes to our ageing dimensions. The issue stems from not being able to reorder columns in Oracle. So your new attributes either sit at the bottom of the table (not good) or yo

Duplicating Dimension Attributes
I have an accumulating fact table tracking the lifecycle of what we refer to as a "Case" in my organization. Each "Case" has a set of 9 specific events, for which we are tracking dates, and the measures in the fact table are the

Question - Nulls as Dimension Attributes
I'm wondering if this is a common practice to add the following 2 'standard' attributes to dimension tables. For example: I have a TRANSACTION_DIM table, I have these 2 'standard' attributes (plus the rest of the business attributes)

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

Deriving Dimension attributes from Fact table
Hi, I have a Customer_Activity fact table which stores the the Activity Start & End Date values. I need to derive the last time the customer had an activity before the current date (based on the Activity End Date - MAX(Activity End Date) WHERE Activity

Dimension Attributes and Fact attributes storing same data in multiple data marts??
Can data marts using BUS architecture store the same data but be called different names like DimChargeToDept and DimDepartment. All have the same attirbutes names different but same exact data and rows. I would rather they create a view for each

How to Handle Data that serves as both a dimension and attributes of another dimension
I have a invoicing warehouse with two fact tables. First is an invoice header fact table which reports on invoice totals and includes a surrogate key for a stat code that was assigned to the invoice. The grain is one row per invoice. Next is a part