OLAP维度结构
我有维度“客户”。每个客户可以有一些业务单位和一些部门。 我应该建立 2 个层次结构：客户 -> 部门和客户 -> 业务单位。 所以，我还需要设置关键属性。这是我的问题：应该使用什么作为关键属性？ 我可能做错了吗？ 你能帮忙吗？
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
要定义层次结构，您应该问以下问题：
如果我对部门进行分组，我有一个消费者吗？如果我将业务分组，我就有消费者了吗？
如果我把部门和业务分组，我就有消费者了？
如果对部门进行分组得到一个消费者，那么层次结构是：消费者>消费者。部门。另一个也同样如此。
如果将部门和业务（维度中包含两条信息的属性，例如DPT1-BUS1）分组得到消费者，则层次结构为：消费者>消费者。部门_业务。
不建议维度中包含空属性。所以要确保消费者需要有一个企业和一个部门。否则，重新表述数据仓库的建模。一般来说，关键维度是人工关键自动递增...
我建议阅读 Kimball希望
这有帮助。
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.