OLAP尺寸结构 [英] OLAP Dimension structure

问题描述

我有客户"维度.每个客户可以有一些商务部门和一些部门. 我应该定义2个层次结构:客户"->部门"和客户"->业务部门". 因此，我还需要设置key属性.这是我的问题:什么应该用作键属性? 可能我做错了吗? 你能帮忙吗?

解决方案

要定义层次结构，您应该提出以下问题:

如果我将部门分组，那么我有消费者吗?如果我将业务分组，那么我有消费者吗? 如果我将部门和业务分组，那么我有消费者吗?

如果将部门分组会得到一个消费者，则层次结构为:消费者">部门".与其他类似. 如果将部门和业务分组(维中包含两个信息的维的属性，例如DPT1-BUS1)来获得消费者，则层次结构为:消费者> Department_Business.

不建议在维度中使用空属性.因此，请确保消费者需要有业务和部门.否则，请改写数据仓库的建模.通常，密钥尺寸是人为的密钥自动递增...

我建议您阅读 Kimball

希望获得帮助.

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?

解决方案

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.

这篇关于OLAP尺寸结构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！