12:28 PM
Kinsz
Data warehouse architecture refers to the nature of the warehouse, its features, as well as its functions. There are three main features of data warehouse design:
Data architecture relates to business processes. In a business, there are basic processes such as inventory, billing, paying, shipping, and so on. The architecture of the system itself demands these processes. Without the customers, there can be no orders; without consumer demand, there can be no billing or shipping; and without paying consumers, there would be no paid workers for data mining architecture.
The next aspect of data architecture is infrastructure. If you are concerned with running only a single application, your infrastructure need not be as strong as someone who creates a sophisticated data network. However, if you like to use your infrastructure for complex data over long periods of time, you may need to do some study or conduct some tests on your computer desktop to check if the data system is performing well. The importance of the infrastructure can be seen in the truth that data warehouses are created not only to store relevant data, but to distribute data to users.
The third feature, the technical area, is the place where the data is converted, cleansed (if need be), and interacts with computer technology before its output. This requires the steps of staging and integration. The data staging process involves five steps:
In extraction, the data must be sorted out from unwanted data and combined. Data is transformed by conversion into the necessary form and interacts with other operations within the system. The data are freshly combined then joined to more data. In the loading phase, the information is preparing to go online for user access.
Security is where the appropriate measures are established to avoid fraud and hacking techniques. One good security measure is the administrator's access-granting only administrators access to selected files. Data encryption policies prevent computer fraud and computer hacking on your network, also. Lastly comes job control, where a function is made that monitors the days and times of workers (job scheduling), logging in and out of the system (which keeps track of times and schedules), and also data access to select individuals in case of an emergency. These data warehouse concepts are important to know.
Frequently, when businesses are drafting data warehouse architecture, they adopt the Zachman model. The Zachman model, named after John Zachman, was invented while Zachman worked at IBM in the 1980s. The Zachman model typically comes in a 6 x 6 matrix, with one row giving six communication questions of who, what, when, where, how, and why, as well as six rows of program transformation: conceptual, contextual, logical, physical, and detailed. Alternatively, businesses could use a more simple model than this.
A data warehouse architecture diagram is a comprehensive drawing of the business processes of a company. There are 5 centrally important data warehouse architecture types (and thus, main diagrams): Independent data marts, data mart bus architecture, hub-and-spoke, centralized data warehouse, and federated architecture.
The independent data mart architecture includes some basic units:
The source systems, origins of data, give way to the staging area where the information is collected, sorted, combined, and then released in small units to the desktop user in specific applications.
Mart bus architecture incorporates a few basic units: source systems, staging area, dimensionalized data type marts, and end-user access and applications.
Data architecture relates to business processes. In a business, there are basic processes such as inventory, billing, paying, shipping, and so on. The architecture of the system itself demands these processes. Without the customers, there can be no orders; without consumer demand, there can be no billing or shipping; and without paying consumers, there would be no paid workers for data mining architecture.
The next aspect of data architecture is infrastructure. If you are concerned with running only a single application, your infrastructure need not be as strong as someone who creates a sophisticated data network. However, if you like to use your infrastructure for complex data over long periods of time, you may need to do some study or conduct some tests on your computer desktop to check if the data system is performing well. The importance of the infrastructure can be seen in the truth that data warehouses are created not only to store relevant data, but to distribute data to users.
The third feature, the technical area, is the place where the data is converted, cleansed (if need be), and interacts with computer technology before its output. This requires the steps of staging and integration. The data staging process involves five steps:
In extraction, the data must be sorted out from unwanted data and combined. Data is transformed by conversion into the necessary form and interacts with other operations within the system. The data are freshly combined then joined to more data. In the loading phase, the information is preparing to go online for user access.
Security is where the appropriate measures are established to avoid fraud and hacking techniques. One good security measure is the administrator's access-granting only administrators access to selected files. Data encryption policies prevent computer fraud and computer hacking on your network, also. Lastly comes job control, where a function is made that monitors the days and times of workers (job scheduling), logging in and out of the system (which keeps track of times and schedules), and also data access to select individuals in case of an emergency. These data warehouse concepts are important to know.
Frequently, when businesses are drafting data warehouse architecture, they adopt the Zachman model. The Zachman model, named after John Zachman, was invented while Zachman worked at IBM in the 1980s. The Zachman model typically comes in a 6 x 6 matrix, with one row giving six communication questions of who, what, when, where, how, and why, as well as six rows of program transformation: conceptual, contextual, logical, physical, and detailed. Alternatively, businesses could use a more simple model than this.
A data warehouse architecture diagram is a comprehensive drawing of the business processes of a company. There are 5 centrally important data warehouse architecture types (and thus, main diagrams): Independent data marts, data mart bus architecture, hub-and-spoke, centralized data warehouse, and federated architecture.
The independent data mart architecture includes some basic units:
The source systems, origins of data, give way to the staging area where the information is collected, sorted, combined, and then released in small units to the desktop user in specific applications.
Mart bus architecture incorporates a few basic units: source systems, staging area, dimensionalized data type marts, and end-user access and applications.
0 comments:
Post a Comment