The Community for Technology Leaders
Green Image
Issue No. 12 - December (2001 vol. 34)
ISSN: 0018-9162
pp: 76-79
<p>Most operational systems store data in a normalized model in which certain rules eliminate redundancy and simplify data relationships. While beneficial for the online transaction processing workload, this model can inhibit those same OLTP databases from running analytical queries effectively. Because the analytical systems did not need to support the OLTP workload, many developers began preplanning for the answer sets. Preplanning, however, created problems in four areas: creating summary tables of preaggregated data, placing indexes in the system to eliminate scanning large data volumes, putting data into one table instead of having tables that join together, and storing the data in sorted order. All these activities require prior knowledge of the analysis and reports being requested. Unfortunately, most data warehouse implementations ignore the longer-term goals of analysis and flexibility in the rush to provide initial value. Taking time to consider the project's real purpose, then building a correct foundation for it, can assure a better future for the data warehouse. The implementers, not the user community, should decide whether to use a summary table or functional model. However, the users, not the IT group, must determine which capability needs must be delivered to drive business opportunity.</p>
Rob Armstrong, "Seven Steps to Optimizing Data Warehouse Performance", Computer, vol. 34, no. , pp. 76-79, December 2001, doi:10.1109/2.970580
90 ms
(Ver 3.3 (11022016))