Building the Data Warehouse

Скачать в pdf «Building the Data Warehouse»

■    Pinpointing when the data warehouse is being used

■    Recognizing how much of the data warehouse is being used

■    Examining the level of usage of the data warehouse

If the data architect does not know the answer to these questions, he or she can’t effectively manage the data warehouse environment on an ongoing basis.

As an example of the usefulness of monitoring the data warehouse, consider the importance of knowing what data is being used inside the data warehouse. The nature of a data warehouse is constant growth. History is constantly being added to the warehouse. Summarizations are constantly being added. New extract streams are being created. And the storage and processing technology on which the data warehouse resides can be expensive. At some point the question arises, “Why is all of this data being accumulated? Is there really anyone using all of this?” Whether there is any legitimate user of the data warehouse, there certainly is a growing cost to the data warehouse as data is put into it during its normal operation.

As long as the data architect has no way to monitor usage of the data inside the warehouse, there is no choice but to continually buy new computer resources-more storage, more processors, and so forth. When the data architect can monitor activity and usage in the data warehouse, he or she can determine which data is not being used. It is then possible, and sensible, to move unused data to less expensive media. This is a very real and immediate payback to monitoring data and activity.

Скачать в pdf «Building the Data Warehouse»