Handling late changes to Type 2 attributes
Hi. I'm trying to find a good way to handle late changes to Type 2 attributes. Please note that I am not asking about early-arriving facts that could be handled with an inferred dimension member. Rather, I am interested in the situation where the dimensio

Insurance Claims
Hi I was reading the Kimball DW Toolkit and need some advice concerning the chapter concernining Claims Processing: Our dataware contains a claims accumulating fact table containing a number of date fields (received date, signed date, entered into

Modeling help on dimension with many boolean value
Hi I'm really stuck on how to model a user need/business need Basically, we are in the healthcare and we have a software that manage the work of the paramedics in ambulances. There is a table that store all standard informations about the work of

multiple hierarchy : single dimension vs multiple
Hi Need to analysis sale revenue by store. We have two separate hierarchy for geographic location 1. Country / County / Council / Store name 2. Country / Region / Area / Store name Need valuable suggestion for how to design dimension for above to

star data model and reporting with different dimension groupings
Dear community, I would like to ask you for helping me with a star data model / reporting problem. The simplified data model is: FACT_SALES (DATE_ID, PRODUCT_ID, CUSTOMER_ID, PLANT_ID, SALES_AMOUNT) DIM_PRODUCT (PRODUCT_ID, PRODUCT_NR,

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

makeing a stand for star schema design
Hi, I am new to a financial company and I was asked to model two new sources of data in the existing mortgage data mart (not too sure if you could actually call it a datamart after seeing the design), basically I was asked to create detail information

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

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

Modeling for Service related facts and dimension (for Tour Operating Company)
I am currently doing a dimensional model design for a Tour operating company. Their business is like selling hotels rooms, flights, and excursion to customers. All these are called SERVICES. Now I am designing dimension and fact table to hold bookings

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

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

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

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

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