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

SET2/Q.1 a. Analyse the role of in-house researcher in marketing research.
Q.1 a. Analyse the role of in-house researcher in marketing research. [3 marks] b. Discuss the purpose of research report with its important characteristics and functions. [7 marks]

SET1/Q.2 a. Outline the role of different types of retailers.
Q.2 a. Outline the role of different types of retailers. (8 marks) b. What is sales forecasting? (2 marks)

Sparse dimensions, how to handle?
I've purchased the book "The Microsoft Data Warehouse Toolkit" and have reviewed it in order to build out a data warehouse solution I am currently designing. I am stuck in a spot that I don't seem to find any examples of , or am not abl

Dates in many dimensions
Hello, I am new to DW. Currently, I am working on a Human Resource database. There are many tables in the source systems which stores dates e.g. dates about contract start, finish, Vacations of an employee, temporary service suspension and many more.

Preserving prior history for late arriving dimensions
Can't find much about this topic anywhere else so hopefully someone can help me. Our warehouse has late arriving dimensions for an Employee. Their department changes, for example, can be backdated in the systems and so we have to account for this and

how many dimensions is too many
If I have a fact table with too many dimensions --- over 30, does that mean I've created dimensions when they could have been attributes to another dimension table or possibly that I am trying to capture too many business processes within one fact table.

Slowly Changing Dimensions - Design Review (Need More Clarification)
Hello, Suppose I have following Fact and Dim table CustomerDim CustomerKey CustomerID CustomerNumber CustomerName CreditLimit - Slowly Changing, wants history IsAnnualMember - Slowly Changing, can be different from year to year or

Hierarchy within single dimension or two dimensions
I am unsure of the best way to model a specific business scenario and was looking for some input. I will explain it in terms of a common example, the Product dimension. Let's say that every "product" is assigned to a specific

Kimball Dimensions
I got into a nice heated debate the other day. The item of discussion was flattened dimensions. I’d like to know your opinion (or facts) about the following, (Some of this is common sense… please still give me some feedback…). Any article citations

Dealing with empty/missing dates in dimensions
I'd like to know other people's opinions on how to deal with missing dates in dimensions, which is a situation that happens quite frequently (for example, think of birth date in a customer dimension). We all know that attributes in dimensions should not

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

Help in declaring grain and identifying dimensions
Requirements: 3 Reports ----------------------- Source Systems: 3 Project DBs 1st Report : Portfolio Summary Details The project monthly details report will display project information i.e. summary actual costs from the Vendor History file

Dimensions Directly Tied to Facts vs. Snowflaking
Hi all, Thanks in advance for your input on this. We are in the midst of a building out a portion of our data warehouse. The example here has to do with insurance data. Hopefully the discussion can be abstracted to a more generic modeling level. We

Date Dimensions - Muliple Calendars
Hi, We have an interesting challenge with our Date dimension. We need to carry multiple calendars - one per country, and one for the Group. When loading the FACT, we create a record per invoice for the country and a record for the group calendars. Thi