当前位置:网站首页>[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:
边栏推荐
猜你喜欢
随机推荐
Flask框架——基于Celery的后台任务
微信小程序,自定义输入框与导航胶囊对其
1004 (tree array + offline operation + discretization)
产品使用说明书小程序开发制作说明
TCP为什么是三次握手和四次挥手?
SWIG教程《四》-go语言的封装
基于ArcGIS水文分析、HEC-RAS模拟技术在洪水危险性及风险评估
640. Solving Equations: Simple Simulation Problems
SYM32——RTC实时时钟程序讲解
易观分析联合中小银行联盟发布海南数字经济指数,敬请期待!
电脑重装系统提示activex部件不能创建对象如何解决
自定义picker滚动选择器样式
小程序-语音播报功能
mysql进阶(三十三)MySQL数据表添加字段
JS入门到精通完整版
消息称原美图高管加盟蔚来手机 顶配产品或超7000元
12海里、24海里、200海里的意义及名称
How to code like a pro in 2022 and avoid If-Else
串口服务器调试助手使用教程,串口调试助手使用教程【操作方式】
$'\r': command not found