I have Dimension "Customer". Each Customer can have some buisness units and some departmens. I should bild 2 hierarchies: Customer->Department and Customer->Buisness Unit. So, I also need to set key attribute. This is my question: What should be use as key attribute? May be I do this wrong? Could you help?
相关问题
- How to calculate the likely size of an OLAP cube
- Distinct count to exclude NULL
- DateAdd Column caused an overflow
- SQL Analysis Services OLAP TIME dimension
- SSAS dimension processing makes underlying measure
相关文章
- Use VBA to select and deselect multiple slicer ite
- Process SSAS cube through c# code
- What should I have in mind when building OLAP solu
- Benefits of using Staging Database while designing
- Can OLAP be done in BigTable?
- C# amo get roles complete
- SSAS tabular model timeout raised during processin
- MDX - TopCount plus 'Other' or 'The Re
To define hierarchies, you should ask the following questions:
If I group the departments, I have a consumer? If I group the business, I have a consumer? If I group the departments and business, I have a consumer?
If grouping the departments get a consumer, so the hierarchy is: Consumer > Department. Similarly with the other. If grouping the department and business (an attribute in dimension that contains two pieces of information, for example, DPT1-BUS1) obtains a consumer, the hierarchy is: Consumer > Department_Business.
It is not recommended to have null attributes in a dimension. So make sure that the consumer needs to have a business and a department. Otherwise, rephrase the modeling of the data warehouse. Generally, a key dimension is a artificial key auto-increment...
I recommend that read Kimball
Hope this help.