EDW和ODS入门 [英] EDW and ODS Getting Started

问题描述

因此，我们了解企业数据仓库和运营数据存储背后的一般概念和基础知识。现在我们正在讨论订单是否"在飞行中"。应该抽到我们的EDW和ODS或者完成
装运订单和与那些已完成的订单相关的所有数据。

有点问题...... EDW应该如何和ODS只包括完整的数据接触点？发货订单？ 

或许可以就此寻找一些意见。我认为我们的一般感觉是为什么用"轮胎踢球者"阻塞EDW和ODS。数据而不是真实的客户数据。毕竟......它应该是EDW和ODS实体....而不是营销数据库。
留下足够好。

感谢您的评论，并希望得到答复。如果这篇文章在错误的论坛中，我会提前道歉并希望得到任何可能存在的优秀EDW-ODS论坛的反馈。

再次感谢。

解决方案

您好ITBobbyP，

是的，EDW理想情况下是报告和数据存储要求的记录存档。新记录可以写入

外部表，一旦达到完成或发送状态，记录就可以移动到内部表。这是ELT概念的一部分：  为Azure SQL数据仓库设计
a PolyBase数据加载策略

您需要创建ODS并将该源作为外部表建立，以便将数据迁移到EDW中。 ODS中的数据从New>经历寿命。发货，然后存档。 ODS中的所有读/写都没有针对SQL DW进行优化，但
更适合Azure SQL数据库或Azure Cosmos DB。

我希望这会有所帮助。

So we understand the general concept and the fundamentals behind an Enterprise Data Warehouse and Operational Data Stores. Now we are having internal discussions as to whether orders "in flight" should be pumped to our EDW and ODS or completed shipped orders and all the data associated with those completed, shipped orders.

Kind of begs the question...Should the EDW and ODS only include completed data touch points? Shipped orders? 

Just maybe looking for some opinions on this is all. I think our general feeling is why clog up the EDW and ODS with "tire kicker" data rather than true customer data. After all...it's supposed to be an EDW and ODS entity....not a marketing database. Leave well enough alone.

Thanks for your review and am hopeful for a reply. And if this post is in the wrong Forum, I apologize in advance and would appreciate feedback of any good EDW-ODS Forums that may exist out there.

Thanks Again.

解决方案

Hi ITBobbyP,

Yes, the EDW would ideally be an archive of records for reporting and data storage requirements. New records could be written to an external table and once reaching a completed or shipped status, the record could be move to an internal table. This is part of the ELT concept: Designing a PolyBase data loading strategy for Azure SQL Data Warehouse

You would need to create the ODS and establish that source as the external table for data migration into EDW. Data in the ODS undergoes a lifespan from New > Shipped and is then archived. All those read/writes in the ODS are not optimized for SQL DW but are better suited for Azure SQL Database or Azure Cosmos DB.

I hope this helps.

这篇关于EDW和ODS入门的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！