数据仓库：建模工作负载分配
我们有一个系统可以跟踪工作单元的分配，从接收该工作单元到完成该工作单元。
一个工作单元有许多属性，它的来源，它的类型等。我对建模相当满意，这些属性可能是事实的维度，也可能只是属性，具体取决于它们的性质以及我们的用户希望报告的方式在他们身上。
问题是分配。
一个工作单元可能会流经多个团队，在这些团队内它可能会流经多个个人。可以对该工作单元执行操作。
我们的用户将会有兴趣对此进行报道。
例如，在特定时间段内按团队分配了多少工作单元。
我是数据仓库的新手，所以我不确定如何对此进行建模。到目前为止，我已经确定的候选者是：
1) 缓慢变化的维度，
可能使用类型 4，用于分配给团队和团队内的人员。
2) 快照
具有主要事实的类型 4 from/to 属性，说明它何时在帐户中，因此每个工作单元在将填充多维数据集的事实表中出现多次。
3）累积快照
我不确定我是否理解这是什么，并且我不确定它是否相关。
有很多东西，比如这个 SCD、团队、团队成员、状态、工作单元的队列分配等。所以这似乎是相当数量的 SCD。
我的选项列表中是否还遗漏了其他内容？我是否从根本上误解了某些东西？
We have a system that tracks the allocation of a unit of work, from receiving that unit of work till completing that unit of work.
A unit of work has a number of attributes, it's source, it's type etc. These I'm fairly ok with modelling, likely to be either dimensions of the fact or just attributes depending on the nature of them and how our users will desire reporting on them.
The problem is the allocation.
A unit of work may flow through multiple teams, within those teams it may flow through multiple individuals. Actions may be carried out on that unit of work.
And our users will be interested in reporting on this.
How many units of work were allocated, by team, in a specific time period for example.
I'm new to data warehousing, so I'm not sure how to model this. The candidates I've identified so far are:
1) Slowly Changing Dimensions
Using probably a Type 4, for the allocation to team and person within team.
2) Snapshot
Having Type 4 from/to attributes of the main fact that say when it was in account, so each unit of work occurs multiple times in the fact table that will populate the cube.
3) Accumulating Snapshot
I'm not sure I understand what this is, and I'm not sure it's relevant.
There are a number of things that would be like this SCD, team, team member, status, queue allocation of unit of work etc. So that seems to be a fair number of SCDs.
IS there something else I've missed in my list of options? Have I fundamentally mis-understood something?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果我理解正确的话，一个工作单位可以采取多项行动来完成。首先，我会选择一个只有一个动作的事实表。
这将 dimPerson 显示为类型 2 维度，它也可以作为类型 1，只要
CurrentTeamKey< /code> 在插入时被复制到事实表的TeamKey中。If I understand correctly, one work unit can take several actions to complete. To start, I would choose a fact table with a grain of one action.
This shows dimPerson as type 2 dimension, it would also work as type 1, as long as
CurrentTeamKeyis copied into theTeamKeyof the fact table on insert.