EDW时间维度的最佳实践 [英] Best Practice for Time Dimension for EDW

问题描述

我正在使用Azure SQL DW构建EDW。数据源是CRM和ERP等。对于某些业务控制器需求，EDW将有出口，但主要是通过Power BI驱动的Azure Analysis Services进行最终用户访问。事实表使用日期时间，并且
通常是Fact表中的几个日期时间列。 

I'm building EDW with Azure SQL DW. Data sources are CRM and ERP etc. There will be excel export from EDW for certain Business Controller needs, but mainly end-user access via Power BI powered Azure Analysis Services. Fact tables are using datetime and there are usually several datetime columns in Fact table. 

现在EDW的最佳做法是什么？日历/时间维度应该建立在EDW还是Azure Analysis Services上？

Now what is best practise for EDW? Should Calender/Time dimentions build on EDW or Azure Analysis Services?

如果应该在EDW上构建什么应该用作加入Fact和DimTime的密钥？ BigInt或Date？

If it should be built on EDW what should be used as key to join Fact and DimTime? BigInt or Date?

Kenny_I

推荐答案

嗨Kenny，

Hi Kenny,

请查看Azure Modern Data Warehouse解决方案体系结构（链接）作为设计解决方案的起点。 

Please take a look at the Azure Modern Data Warehouse solution architectures (Link) as a starting point for designing a solution. 

全部数据加载注意事项（链接需要考虑以了解不同的架构选择如何影响加载功能。 

All data loading considerations (Link) need to be taken into account to understand how different schema choices affect loading capabilities. 

可以通过Azure Active Directory管理用户以实现集中访问可管理性（链接）。

Users could be managed through Azure Active Directory for centralized access manageability (Link).

有一个资源可用于详细说明Azure SQL Data Warehou se和Power BI集成：Azure SQL数据仓库集成（链接）。

There is a resource available to detail the Azure SQL Data Warehouse and Power BI integration: Azure SQL Data Warehouse Integration (Link).

最后，下面讨论了不同的
Distribution 选项;每个具有特定用例的情况都会受益最多。与
一起
表设计注意事项。

And finally, the following discusses the different Distribution options to choose; each having a specific use case it benefits the most. Along with Table design considerations.

需要考虑的一些事项，请继续提出其他问题。 

A few things to consider and please do continue to ask additional questions. 

这篇关于EDW时间维度的最佳实践的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！