当前位置:网站首页>[Data warehouse design] Why should enterprise data warehouses be layered?(six benefits)
[Data warehouse design] Why should enterprise data warehouses be layered?(six benefits)
2022-08-10 15:06:00 【Qingpingle's technical column】
I. Should the data warehouse be layered?
Since the data warehouse is the place where data is stored and calculated, why do you need tiering?It is also the data scale, which is determined by the business scenario.It can be said that when the data warehouse construction of many companies is just starting, most of the data is subjected to rough data access. After ETL is performed, it is directly connected to the business, and reports are generated or imported into the business system for direct use.
Later, with the development of the company's business, the precipitation of data, and the development of the data warehouse to a certain stage, it was found that the use of data was disorganized and various businesses were directly calculated from the original data.This results in various repeated calculations (maybe the two tables are only a few fields apart, but everyone ran it once), which seriously wastes computing resources and storage resources, and costs enterprises a great deal.At this time, everyone has to think about how to standardize storage and computing, and how to minimize enterprise costs.In particular, companies with larger data scales have stronger demands.
Of course, your company's data scale is small, and it is not necessary to have no layering. Of course you can.There is no need to implement such norms. The disadvantage of norms is that they have to pay a lot of labor costs to implement norms and supervise the implementation of norms.The final choice should be considered in combination with the cost of your business, and everything should be based on reality.
Second, the benefits of data warehouse layering
1. Clear data structure:
Each data layer has its scope, so that we can more easily locate and understand when working with tables.
2. Data bloodline tracking:
In simple terms, it can be understood in this way. What we finally give to the business integrity is a business table that can be used directly, but there are many sources of it. If there is a problem with a source table, we hope to be able to quickly and accurately locate it.problem and understand the scope of its harm.
3. Reduce repetitive development:
边栏推荐
猜你喜欢
随机推荐
解题-->在线OJ(十九)
numpy.meshgrid()理解
领域驱动模型设计与微服务架构落地-从项目去剖析领域驱动
SWIG教程《四》-go语言的封装
Understanding_Data_Types_in_Go
基于inotify实现落盘文件的跨进程实时读写交互
使用Uiautomator2进行APP自动化测试
Meaning and names of 12 nautical miles, 24 nautical miles and 200 nautical miles
Epoll learn to think: a high performance server processing framework
Lilac Garden
antd组件中a-modal设置固定高度,内容滚动显示
Flask框架——基于Celery的后台任务
Azure IoT Partner Technology Empowerment Workshop: IoT Dev Hack
Zhaoqi Technology Innovation High-level Talent Entrepreneurship Competition Platform
redhat替换yum源时redhat.repo无法删除或无法禁用的问题解决方法
中学数学建模书籍及相关的视频等(2022.08.09)
蓝帽杯半决赛火炬木wp
SWIG教程《一》
Mini Program-Voice broadcast function
Basic learning of XML









