Customer Dimension

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,

Addresses in Customer Dimension

As part of an Orders dimensional model, I am attempting to design the Customer Dimension table. The customers have multiple sold-to addresses and multiple ship-to addresses. While the OLTP allows any Order to have any combination of sold-to and ship-to

Customer Dimension with Unlimited Metadata

Im currently attempting to define a customer dimension that has a fixed set of fields as well as an unlimited number of user-defined fields. The user-defined fields can be of various data types defined by the user. For example, a user may define a fiel

desining customer Dimesnion

Hi All, I design customer dimensions, but in our concept we have two types of customer the customer as the owner and the customer as one member in customer group which we call it contract,and some times the contract is the owner One-To-one . From this

Bridge Table and Customer Hierarchy

Does anyone know of a good detailed reference that discusses populating and maintaining customer hierarchy type bridge tables? The only decent resource I've found is the "The Data Warehouse ETL Tool Kit", but it only briefly shows an example on

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

How to handle a Type I or II dimension with a snowflaked customer sub dimension (kimball book page 337, 338)

Hello, Within Ralph his new book he describes recommanded situations for snowflaking a dimension. His example is a large customer (visitor) dimension. (page 337, 338 and figure 10-6). I find the artical good, but there is missing one part of this

Walkins For Customer Support Executive In HCL Technologies Ltd

Experience:0 – 1 YearsHCL-Technologies Job Title:Customer Support Executive Location:Chennai Education:Graduate – Any Specialization Name Of company:HCL Technologies Ltd Job Description: Position:Customer Support Executive (Non -Voice BP

Audit Dimension Help

Hello all. I'm at the stage now where im building the audit dimension for my warehouse. I am having a little trouble figuring out a few things though. How do you aggregate the data from the error event fact table into the audit dimension? Some records

Supplier Dimension to include Customers & Employees

We are in the process of finalising Dimensions /Facts to be used in Datawarehouse. Already finalised separate dimensions (eg Customer,Supplier,Employee) to handle requirements of Sales,Purchace and Human resourses. During designing Accounts Payable Fact

Dimension loading sources

Hi all, It's about datawarehouse dimension loading : should i load dimension from a master data management referential or from the truth of my business application. In the first case, dimension will be cleaner than in the second case but it will not

fact table as a dimension

Hi I'm presently modeling a data mart and I would like to use a fact table as a dimension for another fact table. Is it something doable and efficient or is there a better way to do that? if yes should i just create a surrogate key and link both

Bridge tables versus massive junk dimensions

I am designing a star schema to store information on hospital stays. This is my first real star schema and things are off to a good start. My fact table is hospital stays. I have a diagnosis dimension. There are multiple diagnoses per stay. Costs are