I recognize 3 areas of interest to my customer:
* Dealership Customers (aka Clients). People who bring their cars to dealerships.
* Dealership Employees. Service Advisors who make service recommendations.
* CompanyX Employees. Account Mgrs who sell the Product to the Dealerships.
1 approach is to have a SINGLE dim called PERSON given all 3 potential dim share common attributes such as Name, Addr, Phone, Email, etc. I have appx 300 CompanyX emp; 50,000 Dlrship emp; & 25,000,000 Clients.
To distinguish each from the other, I could deploy a field called CATEGORY ( C(lient), D(ealership), & X(CompanyX) ) within the Dim. Or I could distinguish each by its Surrogate Key where the Key would have a prefix of C, D, or X at the time it's created. Example, C12345 for Client, D45788 for a Dealer Emp, & X86443 for a CompanyX Emp.
2nd approach: Create separate Dims for each category.
I have service order measures which measure how many Repair OrdersService Orders were sold by a Dealership Employee. I don't envision a case where the measure would use multiple Dims (CLIENT, DEALERSHIP EMP, & Company X EMP). The measures would be separated out, meaning I would have a Client Fact Tbl, a CompanyX Fact Tbl, & a Dealership Fact Tbl.
July 26, 2006 10:45 AM
July 27, 2006 11:20 PM