Monitoring Data Warehouse

In general, two monitored operational components in a data warehouse environment are the use of data and data stored in the Data warehouse. Monitoring data in a data warehouse environment is the basic ability to manage a data warehouse environment. Some important information can be obtained by monitoring data in a data warehouse environment, including:

Identify what is growing, where growth occurs, and what rate of growth occurs

Identify what data is being used.
Estimate the response time that the end user gets.
Determine who is actually using the Data warehouse.
Describes how much data is being used in the Data warehouse.
Accurately indicate when the data warehouse is used.
Identify how much data in the Data warehouse is being used.
Check the hierarchy using the Data Warehouse.
When data architecture designers do not know the answers to these questions, it is not possible to effectively manage a running data Warehouse environment. is monitoring the data warehouse really useful? Just think about how important it is to know what data is being used in the Data warehouse. The nature of the data warehouse is to grow continuously. Historical data is constantly added to the Data warehouse, and the aggregated data is continuously added, and the new Decimation stream is created. At the same time, storage and processing techniques for data warehousing reside are not expensive. Sometimes you ask the question: "Why do all this data accumulate?" Does anyone really use this data? "Obviously, regardless of whether there are legitimate users of the data warehouse, the overhead of the data warehouse increases as the data is put into the data warehouse during the normal operation of the Data Warehouse." As long as the data architect has no way of determining how to use the data in the Data warehouse, there is no choice but to keep buying new computer resources-buying more storage devices, more processors, and so on. But by monitoring the use of data in the Data Warehouse, you have the opportunity to move unused data to other media. It is appropriate to move this data to an inexpensive medium when the data architect discovers that some of the current data is not being used. By monitoring the use and activity of data in the Data Warehouse, data architecture designers can determine what data is currently not being used and can be transferred. monitoring data and activities in a data warehouse environment can be very tangible and prompt.

During data monitoring processing, various profiles that can be used to create data include:
The directory of all tables in the Data Warehouse.
The contents of these tables.
The growth of tables in the Data Warehouse.
The available index directory for accessing the table.
Catalog of summary and summary sources.

The requirements for monitoring data warehouse activities are illustrated by the following issues:
What data is being accessed?
When do you visit?
Who is the visitor?
How often do you visit?
At what level of detail?
What is the response time to the request?
At what time of day does the request be made?
How much data is requested?
is the request terminated or is it a normal end?

One of the fundamental issues with monitoring programs in a data warehouse environment is where to monitor. One place to monitor is the end-user terminal. This is a convenient location for monitoring work because there are a lot of idle machine cycles, and there is only a small impact on the system performance of monitoring work here. However, the end-user terminal monitoring system means that each monitored endpoint needs its own administrator. In a separate D s network, there may be as many as 10 000 terminals, and it is almost impossible to attempt to manage the monitoring of each terminal. Another approach is to monitor the D s system at the server level. Monitoring is not initiated until the query has been formalized and has been passed to the server that manages the data warehouse. There is no doubt that it is much easier to manage the monitoring program here. However, there is a large likelihood of system-wide performance degradation. Because the monitoring program uses server resources, the monitoring program affects the performance of the entire D S data Warehouse environment. The location of the monitoring program is an important issue that must be carefully considered, and the tradeoff between ease of management and reduced performance. One of the most effective uses of monitoring programs is the ability to compare today's results with the average daily results. When an anomaly is found, one can ask "what is the difference between today's average and daily results?" "This is usually good. In most cases, performance changes are not as bad as you might think. But in order to make such comparisons, a "daily average profile" is required. The "Average daily profile" includes important metrics that describe the various criteria for a day in the D s s environment. Once the day's situation is measured, it can be compared with the average daily profile. Of course, the daily average is always changing at any time. Tracking these changes on a regular basis makes sense for long-term system trends to be measured.

Monitoring Data Warehouse