Building the Data Warehouse

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


Unless circumstances are very unusual, the work done for the 1st report does not pave the way for the 2nd report, or the 3rd . . . .


Unless future corporate reporting requirements are known in advance and are factored into building the first corporate report, each new corporate report will probably require the same large overhead! In other words, it is unlikely that the first corporate report will be adequate for future corporate reporting requirements.


Productivity, then, in the corporate environment is a major issue in the face of the naturally evolving architecture and its legacy systems. Simply stated, when using the spider web of legacy systems, information is expensive to access and takes a long time to create.


From Data to Information


As if productivity and credibility were not problems enough, there is another major fault of the naturally evolving architecture—the inability to go from data to


information. At first glance, the notion of going from data to information seems to be an ethereal concept with little substance. But that is not the case at all.


Consider the following request for information, typical in a banking environment: “How has account activity differed this year from each of the past five years?”


Figure 1.7 shows the request for information.


going from data to information

loans


DDA




different element, same name


Next, you run into the lack of integration across applications.


Figure 1.7 “How has account activity been different this year from each of the past five years for the financial institution?»

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