Abstract
Data for decision oriented technologies, like data warehousing and On-Line Analytical Processing (OLAP) systems, are ever increasing. As they store and handle data of historical nature, the volume of data involved could be very large, requiring more efficient ways of dealing with the same. Recent advances in parallel computing and high-speed networks using a cluster of PCs or workstations (COWs) offer a solution for providing this scale up in performance by parallelism of data, and its processing, in the data warehouse. However, there are issues peculiar to clusters that first need to be considered. One of the important issues in the case of a non-dedicated cluster is to adapt itself to the changing environment due to its usage. This paper looks at some of the adaptation strategies that could be applied for data warehousing and OLAP systems implemented on a COW. 1. I N T R O D U C T I O N New decision support technologies such as, data warehousing and on-l ine analytical processing (OLAP) have seen explos ive growth in their usage in recent years [5]. A data warehouse can be defined as an online repository of historical enterprise data that is aimed at enabl ing the knowledge worker (executive, manager, analyst) make better and faster decis ions [4, 6]. There are, mainly, two reasons for using a data warehouse, viz. management of historical data and better performance. While the operational database is tuned to handle the day to day operations of the organisation, the data warehouse is geared to facilitate the management ' s ad-hoc queries for decision-making. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies arc not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and or fee, SAC'00 March 19-21 Como, Italy (c) 2000 ACM 1-58113-239-5/00/003>...>$5.00 Often, knowledge workers need complex analyses and visualisat ion of data. For this purpose, the data in a warehouse is typically modeled multidimensionally [10]. For example, in a product sales data warehouse, date, product code, region, salesperson and customer might be some of the dimensions of interest, while detailed information regarding each sale (total price, quantity etc.) is recorded in a fact table. Figure 1 shows an example of such a database schema, called a star schema. Some of these dimensions may be hierarchical. For example, date of sale may be organised as a month-quarter-year hierarchy. The operat ions of OLAP allow users to efficiently retrieve data from the data warehouse and are quite different to those of on-line transaction processing (OLTP). Typical OLAP operations include rollup (increasing the level of aggregation; for example, sales for a whole year rather than by quarters) and drill-down (decreasing the level of aggregation or increasing the detail) along one or more dimension hierarchies, slice-and-dice (selection and projection) and pivot (re-orienting the mult idimensional viewing of data) [10]. Due to these differences in requirements of the nature of applications and operations on a data warehouse, the typical operational database would not be able to provide an acceptable level of performance for OLAP queries. Also, the nature of data required for decision support may be missing from such a database (for example, to show trends in sales for a certain region or city over the years we need historical data which is not available in a typical operational database). As data in a data warehouse keeps on increasing so does the need for faster methods of accessing and processing the data. However, even if we increase the speed of the processor (CPU) the steep growth of large data warehouses, will eventually surpass the capability based on the available processing speed. This forces us to look into alternative methods in speeding up the processing of OLAP and other types of queries on a data warehouse. Faster processors and more efficient algorithms of query evaluation can help, but only to a certain extent. A number of techniques [11, 15, 16] have been suggested by the researchers to speed up the query processing in OLAP. Some of these techniques
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.