Textual fact or Junk dimension?
Hello, I have been following the forum for a while now and I must say that many doubts about dimensional modeling have gone thank to you all. However I am facing now the modeling of a cube and I am somewhat stuck on what is the best

Employee With Multiple Jobs
Hello; I am developing an Employee Transaction Dimension such as that seen in Figure 8.2 of the "The Data Warehouse Toolkit". In my case, an employee may have multiple jobs. Some of the attributes found in the Employee Transaction Dimension

Multi enterprise Calendar Dimension
Current I'm working for a Enterprise organisation that provide multiple vendors over the world with contract information. My question is what is the best practice for creating a Calendar structure that can support multiple different time zones and fiscal

Cube Processing for Dimension Schema changes
Hi, I had a general question about how cube processing works. If my dimension schema changes (an addition of a property), will I have to do a full reprocess of all cube partitions for which that dimension was member of? Or do I only need to

De-normalizing Customer Information to create a Customer Dimension
I have a question regarding de-normalizing customer data to create a single customer dimension! Let's say our OLTP customer information is made up of 2 tables. 1) Customer Table (customer name, customer type, etc...) 2) Address Table (address1,

Tracking Type2 SCD when using a dimension outrigger
With an outrigger table, a narrow band of attributes, usually with significantly lower cardinality than the main dimension, is in essence snow flaked off of the main dimension. Great technique for data management and maintenance. To hide complexity from

Issue with modelling a hierarchy so the OLAP cube build is efficent
I am faced with a nasty which seems to have no neat solution within dimensional modelling. (This could well be just me being brain dead and dumb). Background: We are a major commercial bakery company. Having re-developed and released the first two

Kimball or not Kimball type 2 dimension (sk as primary key)
We're using Oracle and I received the following (see below) from our architect about why we shouldn't create a new SK for every type 2 change. i.e. use a combination of date and sk as the primary key. Is this correct. Will it affect the creation of

Slowly Changing Dimension table
Hello, I have scenario where we are creating a Dimension Table and Fact Table from the same Source Table which contains both descriptive and numeric data I want to model the Dimension table as a Slowly changing Dimension Type 2 (create new

Conformed Dimension Processing Multiple Data Marts
Rookie question. We have 8 conformed dimensions and we are on our 4th data mart using some of these 8 conformed dimensions. We build the conformed dimensions once every night because the client wants to complete full refresh only. The client has

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

Drill-across relationships (Invoices -> Payments etc.)
I have a question regarding the relationship between fact tables to enable drill-across between these. I have a number of fact tables in my design, Invoices and Payments, are two of them. Invoices contain invoice amounts per invoice row. InvoiceNumber

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

Large Dimension table compared to fact table?
I may be misguided in my attempt to make a dimensional model here, but I will explain the scenario. We provide a value add service in the supply chain business...in this case by depicting a scorecard of the accuracy of vendors' product sizing

Audit dimension for a dimension?
The books describe how to create a useful audit dimension for the fact table rows, but what about the dimension table rows? Why isn't that mentioned in the books? Isn't the data quality and lineage also important for dimensions? Would you create a