不同更新时间表的事实表 [英] Fact Table with Different Update Schedules
问题描述
提供已经存在的措施在第二步没有修改,您可以将事实表视为累积快照。
该表描述了具有确定性开始和结束类型的工作流的流程。在Kimball的数据仓库工具包中查找它,或者只是GoogleKimball累积快照事实表。
I have two sets of data with the same level of grainularity, for example invoice number. Most of the data required is updated daily as we recognize the revenue for previous invoices. However, some of this data is fed through a seperate costing system once a month and is then fed to the data warehouse with additional information. Should I create one fact table that contains both sets of data, and then run an update on the fact table once a month when the other data is imported in, or should I create two fact tables because of the different update schedule. The data is related, and many queries (~35%) will want information from both sets of data (when avaliable). The system imports 30,000 rows a day into the fact table has about 38,000,000 rows in it, the monthly update would affect 660,000 rows.
Providing that already existing measures are not modified in the second step, you could treat the fact table as an "accumulating snapshot". The table describes processes with a definitive start and the end -- kind of workflows. Look it up in Kimball's Data Warehouse Toolkit or just Google "Kimball accumulating snapshot fact table".
这篇关于不同更新时间表的事实表的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!