Data Warehouse and OLAP | Data Warehouse | Information Management


2: Data Warehouse and OLAP Technology for Data Mining
• What is a data warehouse? • A multi-dimensional data model • Data warehouse architecture • Data warehouse implementation • Further development of data cube technology • From data warehousing to data mining


What is Data Warehouse?
• Defined in many different ways, but not rigorously.
– A decision support database that is maintained separately from the organization’s operational database. – Support information processing by providing a solid platform of consolidated, historical data for analysis. – W. H. Inmon — “A data warehouse is a subject-oriented, integrated, time-variant, and nonvolatile collection of data in support of management’s decision-making process.”

• Data warehousing:
– The process of constructing and using data warehouses


Data Warehouse — Key Features (1)
• Subject-Oriented:
– Organized around major subjects:
• E.g., customer, product, sales. • Focusing on the modeling and analysis of data for decision makers, not on daily operations or transaction processing. • Provide a simple and concise view around particular subject issues by excluding useless data in the decision support process.

• Integrated:
– Constructed from multiple, heterogeneous data sources:
• RDBs, flat files, on-line transaction records, …

– Applying data cleaning and data integration techniques.
• Ensure consistency in naming conventions, encoding structures, attribute measures, etc. among different data sources • E.g., Hotel price: currency, tax, breakfast covered, etc.

– When data is moved to the warehouse, it is converted.

Data Warehouse — Key Features (2)
• Time Variant:
– The time horizon for the data warehouse is significantly longer than that of operational systems.
• Current value data ⇔ historical perspective info. (past 5-10 yr).

– Every key structure in the data warehouse:
• Contains an element of time [explicitly or implicitly], • But the key of tuples may or may not contain “time element”.

• Non-Volatile:
– A physically separate store of data transformed (copied) from the operational environment into one semantic data store.
• Operational data update does not occur in data warehouse. • Require no transaction processing, recovery, and concurrency control mechanisms. [⇐ on-line database operations]

– Requires only two operations in data accessing:
• initial loading of data and access of data.

Compared w. Heterogeneous DBMS
• Traditional heterogeneous DB integration:
– Build wrappers/mediators on top of heterogeneous DB.
• E.g., IBM Data Joiner and Informix DataBlade.

– Query-driven approach: [costly]
• When a query is posed to a client site, a meta-dictionary is used to translate the query into queries appropriate for individual heterogeneous sites involved, and the results are integrated into a global answer set • Complex information filtering, compete for resources.

• Data warehouse: update-driven, high performance
– Information from heterogeneous sources is integrated in advance and stored in warehouses for direct query and analysis.

accounting. 6 . local ⇔ evolutionary. detailed ⇔ historical. inventory. – Day-to-day operations: purchasing. etc. banking. Operational DBMS • OLTP (on-line transaction processing): – Major task of traditional relational DBMS. – View: current. • OLAP (on-line analytical processing): – Major task of data warehouse system. payroll. integrated. – Access patterns: update ⇔ read-only but complex queries. registration.43] – User and system orientation: customer (query) ⇔ market. – Database design: ER + application ⇔ star + subject. consolidated. manufacturing.Compared w. • Distinct features (OLTP ⇔ OLAP): [ref. – Data contents: current.1 p. – Data analysis and decision making. Table 2.

summarized. consolidated ad-hoc lots of scans complex query millions hundreds 100GB-TB query throughput.OLTP vs. key short.1 p. Table 2. response 7 read/write index/hash on prim. OLAP OLTP users function DB design data usage access unit of work # records accessed #users DB size metric clerk. up-to-date detailed. flat relational isolated repetitive [ref. IT professional day to day operations application-oriented current.43] OLAP knowledge worker decision support subject-oriented historical. multidimensional integrated. simple transaction tens thousands 100MB-GB transaction throughput .

– data quality: different sources typically use inconsistent data representations. codes & formats which have to be reconciled. – data consolidation: DS requires consolidation (aggregation. etc. 8 . summarization) of data from heterogeneous sources. indexing.Why Separate Data Warehouse? • High performance for both systems: [asynchronous] – DBMS ⇒ tuned for OLTP: • access methods. – Warehouse ⇒ tuned for OLAP: • complex OLAP queries. • Different functions and different data: – missing data: Decision support (DS) requires historical data which operational DBs do not typically maintain. recovery. consolidation. concurrency control. multidimensional view.

• Dimensions: time. brand. week. quarter. [group by] 9 . … – Dimension tables. – The top most 0-D cuboid. units_sold. – A data cube. amount_budgeted.. item (item_name. branch. location. allows data to be modeled and viewed in multiple dimensions. month.g. – The lattice of cuboids forms a data cube. dollars_sold.From Tables and Spreadsheets to Data Cubes • Data warehouses utilize an n-dimensional data model to view data in the form of a data cube. • In data warehousing literature.. supplier. • E. – An n-D base cube is called a base cuboid. is called the apex cuboid. • E. year). each for a dimension. – Fact table contains numerical measures (say. time (day. such as sales. item. …) and keys to each of the related dimension tables. type). which holds the highest-level of summarization.g.

supplier 2-D cuboids C34 4 C4 time. item.Cube: A Lattice of Cuboids C 4 0 all time item location supplier 0-D (apex) cuboid 1-D cuboids C14 time.item.location time.supplier item. supplier 10 .supplier 3-D cuboids 4-D (base) cuboid time.item.supplier item.location location.location.supplier time.supplier item.location.location time.item 4 C2 time. location.

11 . – Fact constellations. or Galaxy schema : Multiple fact tables share dimension tables. therefore called galaxy schema or fact constellation. forming a shape similar to snowflake. viewed as a collection of stars.Conceptual Modeling of Data Warehouses • Modeling data warehouses: dimensions & measures – Star schema: A fact table in the middle connected to a set of dimension tables – Snowflake schema: A refinement of star schema where some dimensional hierarchy is normalized into a set of smaller dimension tables.

Example of Star Schema time time_key day day_of_the_week month quarter year item Sales Fact Table time_key item_key branch_key location_key units_sold dollars_sold avg_sales item_key item_name brand type supplier_type branch branch_key branch_name branch_type location location_key street city province_or_street country Measures 12 .

Example of Snowflake Schema time time_key day day_of_the_week month quarter year item Sales Fact Table time_key item_key branch_key location_key units_sold dollars_sold avg_sales location location_key street city_key item_key item_name brand type supplier_key supplier supplier_key supplier_type branch branch_key branch_name branch_type city city_key city province_or_street country Measures 13 .

Example of Fact Constellation time time_key day day_of_the_week month quarter year item Sales Fact Table time_key item_key branch_key location_key units_sold dollars_sold avg_sales item_key item_name brand type supplier_type Shipping Fact Table time_key item_key shipper_key from_location to_location dollars_cost units_shipped branch branch_key branch_name branch_type location location_key street city province_or_street country shipper shipper_key shipper_name location_key shipper_type 14 Measures .

DMQL: Language Primitives • Cube Definition (Fact Table): – define cube <cube_name> [<dimension_list>]: <measure_list> • Dimension Definition (Dimension Table): – define dimension <dimension_name> as (<attribute_or_subdimension_list>) • Special Case (Shared Dimension Tables): – First time as “cube definition” – define dimension <dimension_name> as <dimension_name_first_time> in cube <cube_name_first_time> 15 .A Data Mining Query Language.

avg_sales = avg(sales_in_dollars) – define dimension time as (time_key.Defining a Star Schema in DMQL • Procedure: – define cube sales_star [time. city. month. item. street. branch_name. type. province_or_state. branch. year) – define dimension item as (item_key. quarter. day_of_week. item_name. day. country) 16 . brand. dollars_sold = sum(sales_in_dollars). branch_type) – define dimension location as (location_key. location]: units_sold = count(*). supplier_type) – define dimension branch as (branch_key.

province_or_state. type. branch. city(city_key. supplier_type)) – define dimension branch as (branch_key. dollars_sold = sum(sales_in_dollars). street. brand. quarter. month. supplier(supplier_key. year) – define dimension item as (item_key. avg_sales = avg(sales_in_dollars) – define dimension time as (time_key. country)) 17 . item. day.Defining a Snowflake Schema in DMQL • Procedure: – define cube sales_snowflake [time. item_name. branch_type) – define dimension location as (location_key. day_of_week. branch_name. location]: units_sold = count(*).

city. avg_sales = avg(sales_in_dollars) – – – – define dimension define dimension define dimension define dimension country) time as (time_key. supplier_type) branch as (branch_key. branch. location as location in cube sales. from_location. shipper_name. quarter. province_or_state. month. day_of_week. unit_shipped = count(*) – define dimension time as time in cube sales – define dimension item as item in cube sales – define dimension shipper as (shipper_key. day. item_name. branch_name. location]: units_sold = count(*). brand. street. type. dollars_sold = sum(sales_in_dollars). shipper.Defining a Fact Constellation in DMQL • define cube sales [time. to_location]: dollar_cost = sum(cost_in_dollars). item. shipper_type) – define dimension from_location as location in cube sales – define dimension to_location as location in cube sales 18 . branch_type) location as (location_key. • define cube shipping [time. year) item as (item_key. item.

⇐ derived • Holistic: if there is no constant bound on the storage size needed to describe a sub-aggregate.g. median().g. ⇐ aggregate • Algebraic: if it can be computed by an algebraic function with M arguments (where M is a bounded integer).. min().. – E. min_N(). rank(). standard_deviation(). count(). ⇐ statistical 19 .Measures: Three Categories • Distributive: if the result derived by applying the function to n aggregate values is the same as that derived by applying the function on all the data without partitioning.g.. each of which is obtained by applying a distributive aggregate function. mode(). avg(). – E. max(). sum(). – E.

Toronto M.... Chan ..A Concept Hierarchy: Dimension (location) Higher: more general concepts all region country city office Germany Europe .. Wind 20 Lower: more specific concepts . all .. North_America Canada .... L... Mexico Spain Frankfurt . Vancouver ..

week} < year • Set_grouping hierarchy – {1.View of Warehouses and Hierarchies Specification of hierarchies • Schema hierarchy – day < {month < quarter..10} < inexpensive Year Quarter Month Week Day 21 .

Time gio n Industry Category Region Country City Office Year Quarter Month Week Day Product Re Product Month Hierarchical summarization paths 22 . Dimensions: Product.Multidimensional Data • Sales volume as a function of product. Location. month. and region.

A Country Canada Mexico sum Pr 23 . U.A Sample Data Cube Date od uc t TV PC VCR sum 1Qtr 2Qtr 3Qtr 4Qtr sum Total annual sales of TV in U.S.A.S.

date date. country 3 C3 3-D(base) cuboid 24 .Cuboids Corresponding to the Cube C C C 3 0 all 0-D(apex) cuboid product 3 1 date country 1-D cuboids 3 2 product. country 2-D cuboids product. date.

Browsing a Data Cube • Visualization • OLAP capabilities • Interactive manipulation 25 .

Fig.10 p.59 • Roll up (drill-up): summarize data – by climbing up hierarchy or by dimension reduction. – drill through: through the bottom level of the cube to its back-end relational tables (using SQL). 3D to series of 2D planes. 2. • Slice and dice: project and select. or introducing new dimensions. 26 .Typical OLAP Operations ref. • Pivot (rotate): – reorient the cube. • Drill down (roll down): reverse of roll-up – from higher level summary to lower level summary or detailed data. • Other operations – drill across: involving (across) more than one fact table. visualization.

Shipping Method Customer Orders CONTRACTS AIR-EXPRESS TRUCK Time ANNUALY QTRLY DAILY CITY COUNTRY DISTRICT REGION Location Promotion DIVISION Organization 27 Customer ORDER PRODUCT LINE Product PRODUCT ITEM PRODUCT GROUP SALES PERSON .A Star-Net Query Model Each circle (abstract level) is called a footprint.

stored. 28 . – Data warehouse view: • consists of fact tables and dimension tables. – Business query view: • sees the perspectives of data in the warehouse from the view of end-user.Design of a Data Warehouse: A Business Analysis Framework • Four views regarding the design of a data warehouse: – Top-down view: • allows selection of the relevant information necessary for the data warehouse. and managed by operational systems. – Data source view: • exposes the information being captured.

Data Warehouse Design Process • Top-down. quick turn around. – Bottom-up: Starts with experiments and prototypes (rapid). short turn around time. – Spiral: rapid generation of increasingly functional systems. – The measure that will populate each fact table record. bottom-up approaches or hybrid: – Top-down: Starts with overall design and planning (mature). 29 . • From software engineering point of view: – Waterfall: structured and systematic analysis at each step before proceeding to the next. • Typical data warehouse design process: Choose – A business process to model. e. invoices. – The dimensions for each fact table record. … – The grain (atomic level of data) of the business process.g. orders..

Multi-Tiered Architecture Metadata other Monitor & Integrator OLAP Server sources Operational Extract Transform Load Refresh Data Warehouse Serve Analysis Query Reports Data mining DBs Data Marts Data Sources Data Storage 1 OLAP Engine Front-End Tools 2 3 30 .

selected groups. 31 . – Only some summary views are materialized. • Data Mart: – a subset of corporate-wide data that is of value to a specific groups of users. • Virtual warehouse: – A set of views over operational databases. such as marketing data mart. dep.1 Three Data Warehouse Models • Enterprise warehouse: – collects all of the information about subjects spanning the entire organization. (directly from warehouse) data mart. • Its scope is confined to specific. – Independent vs.

Data Warehouse Development: A Recommended Approach Multi-Tier Data Warehouse Distributed Data Marts Data Mart Data Mart Enterprise Data Warehouse Model refinement Model refinement Define a high-level corporate data model 32 .

– greater scalability. – fast indexing to pre-computed summarized data.2 OLAP Server Architectures • Relational OLAP (ROLAP): – Use relational or extended-relational DBMS to store and manage warehouse data and OLAP middle ware to support missing pieces. low level: relational. implementation of aggregation navigation logic. e. high-level: array. and additional tools and services. – Include optimization of DBMS backend.g. • Multidimensional OLAP (MOLAP): – Array-based multidimensional storage engine (sparse matrix techniques).. • Hybrid OLAP (HOLAP): – User flexibility. • Specialized SQL servers: – specialized support for SQL queries over star/snowflake schemas. [Informix’s Red-brick] 33 .

year. year) 34 .product). product. city. year () (item) • Need to compute these Group-By’s: (city) (year) 2 – (date. city. SUM(amount) FROM SALES CUBE BY item. year]: sum(sales_in_dollars) – compute cube sales • Transform it into a SQL-like language (with a new operator cube by. customer). year) (customer). item. (product. (city. (city.’96): – SELECT item. (date. introduced by Gray et al. customer).Cube Operation • Cube definition and computation in DMQL: – define cube sales[item. year) (date. city. (date). (). (product). (item. item) (city. n customer).

or some (partial materialization). if Li = 1. 35 . access frequency. – The top-most cuboid (apex) contains only one cell. none (no materialization). etc. sharing.Efficient Data Cube Computation • Data cube can be viewed as a lattice of cuboids: – The bottom-most cuboid is the base cuboid. • Based on size. n • Materialization of data cube: – Materialize every (cuboid) (full materialization). – How many cuboids in an n-dimensional cube with Li levels? T = ∏ i =1 ( Li + 1) ⇒ 2n . – Selection of which cuboids to materialize.

Cube Computation: ROLAP-Based Method (1) • Efficient cube computation methods: – ROLAP-based cubing algorithms (Agarwal et al’96) – Array-based cubing algorithm (Zhao et al’97) – Bottom-up computation method (Bayer & Ramarkrishnan’99) • ROLAP-based cubing algorithms: – Sorting. hashing. – Aggregates may be computed from previously computed aggregates. rather than from the base fact table. 36 . and grouping operations are applied to the dimension attributes to reorder and cluster related tuples. – Grouping is performed on some sub-aggregates as a “partial grouping step”.

VLDB’96) – Smallest-parent: computing a cuboid from the smallest cuboid previously computed. 37 . al. – Amortize-scans: computing as many as possible cuboids at the same time to amortize disk reads. – Share-partitions: sharing the partitioning cost cross multiple cuboids when hash-based algorithms are used. – Share-sorts: sharing sorting costs cross multiple cuboids when sort-based method is used. – Cache-results: caching results of a cuboid from which other cuboids are computed to reduce disk I/Os.Cube Computation: ROLAP-Based Method (2) • This is not in the textbook but in a research paper • Hash/sort based methods (Agarwal et.

offset) • Compute aggregates in “multiway” by visiting cube cells in the order which minimizes the # of times to re-visit each cell. thereby reducing memory access and storage cost.Multi-way Array Aggregation for Cube Computation • Partition arrays into chunks (a small sub-cube fit in memory). C c3 61 62 63 64 c2 45 46 47 48 c1 29 30 31 32 c0 b3 B 13 9 5 1 a0 14 15 16 B b2 b1 b0 2 a1 3 a2 4 a3 60 44 28 56 40 24 52 36 20 ordering What is the best traversing order to do multi-way aggregation? 38 A . • Compressed sparse array addressing: (chunk_id.

Multi-way Array Aggregation for Cube Computation AC BC C c3 61 62 63 64 c2 45 46 47 48 c1 29 30 31 32 c0 B 13 9 5 1 a0 2 a1 3 a2 4 a3 14 15 16 28 24 20 44 40 36 60 56 52 b3 B b2 b1 b0 A b0c0 of BC AB 39 .

Multi-way Array Aggregation for Cube Computation a0b0c0 ⇒ a0b0. b0c0. AC BC C c3 61 62 63 64 c2 45 46 47 48 c1 29 30 31 32 c0 B 13 9 5 1 a0 2 a1 3 a2 4 a3 14 15 16 28 24 20 44 40 36 60 56 52 b3 B b2 b1 b0 A AB A=40 B=400 C=4000 ⇒ AB=16000 ⇒ AC=160000 ⇒ BC=1600000 40 . a0c0.

Multi-Way Array Aggregation for Cube Computation (cont’d) • Method: the planes should be sorted and computed according to their size in ascending order. • Limitation of the method: computing well only for a small number of dimensions – If there are a large number of dimensions. – See the details of Example 2. 75-78) – Idea: keep the smallest plane in the main memory. Store only partitions with aggregate value > threshold 41 . fetch and compute only one chunk at a time for the largest plane. “bottom-up computation” and iceberg cube computation methods can be explored.12 (pp.

Indexing OLAP Data: Bitmap Index • Index on a particular column • Each value in the column has a bit vector: bit-op is fast • The length of the bit vector: # of records in the base table • The i-th bit is set if the i-th row of the base table has the value for the indexed column • not suitable for high cardinality domains Base table Cust C1 C2 C3 C4 C5 Region Asia Europe Asia America Europe Index on Region Index on Type Type RecIDAsia Europe America RecID Retail Dealer Retail 1 1 0 1 1 0 0 Dealer 2 2 0 1 0 1 0 Dealer 3 3 0 1 1 0 0 Retail 4 1 0 4 0 0 1 5 0 1 0 1 0 Dealer 5 42 .

…) • Traditional indices map the values to a list of record ids – It materializes relational join in JI file and speeds up relational join — a rather costly operation fact table • In data warehouses. – E. fact table: Sales and two dimensions city and product • A join index on city maintains for each distinct city a list of R-IDs of the tuples recording the Sales in the city – Join indices can span multiple dimensions. 43 . join index relates the values of the dimensions of a start schema to rows in the fact table.g. S-id) where R (R-id.Indexing OLAP Data: Join Indices • Join index: JI(R-id. …) S (S-id.

g. into corresponding SQL and/or OLAP operations. • Exploring indexing structures and compressed vs. dense array structures in MOLAP. dice = selection + projection • Determine to which materialized cuboids the relevant operations should be applied. etc. roll. e.Efficient Processing OLAP Queries • Determine which operations should be performed on the available cuboids: – transform drill.. 44 .

– The mapping from operational environment to the data warehouse. 45 . • warehouse schema. – The algorithms used for summarization. – Business data. – Data related to system performance. hierarchies. monitoring information (usage statistics. • schema. dimensions. archived. – Operational meta-data. audit trails). charging policies. • data lineage (history of migrated data and transformation path). derived data definitions. or purged). view. ownership of data. It has the following kinds: – Description of the structure of the warehouse.Metadata Repository • Meta data is the data defining warehouse objects. currency of data (active. error reports. • business terms & definitions. view and derived data definitions. data mart locations and contents.

Data Warehouse Back-End Tools and Utilities • Data extraction: – get data from multiple. consolidate. • Load: – sort. check integrity. 46 . compute views. summarize. • Data transformation: – convert data from legacy or host format to warehouse format. • Data cleaning: – detect errors in the data and rectify them when possible. and build indices and partitions. heterogeneous. • Refresh – propagate the updates from the data sources to the warehouse. and external sources.

• Discovery-driven: (Sarawagi et al. based on a statistical model. – Computation of exception indicator (modeling fitting and computing SelfExp.Discovery-Driven Exploration of Data Cubes • Hypothesis-driven: exploration by user. huge search space.’98) – pre-compute measures indicating exceptions. – Visual cues such as background color are used to reflect the degree of exception of each cell. guide user in the data analysis. 47 . InExp. – Exception: significantly different from the value anticipated. at all levels of aggregation. and PathExp values) can be overlapped with cube construction.

Examples: Discovery-Driven Data Cubes more PathExp Drill down high InExp high SelfExp high InExp Drill down 48 .

price = max(price) – Continuing the last example. month}. – Ex. • select item.sales) from purchases Dependent! where year = 1997 grouping variable of group gi cube by item. Grouping by all subsets of {item. region. max(price). et al. 49 . find the maximum price in 1997 for each group. 1998): Compute complex queries involving multiple dependent aggregates at multiple granularities. and the total sales among all maximum price tuples. sum(R. region. month: R such that R. region. among the max price tuples.Complex Aggregation at Multiple Granularities: Multi-Feature Cubes • Multi-feature cubes (Ross. find the min and max shelf life. and find the fraction of the total sales due to tuples that have min shelf life within the set of all max price tuples. month.

deeper analysis. • supports associations. basic statistical analysis. drilling. – Information processing: • supports querying. and presenting the mining results using visualization tools. data mining emphasizes more automation. • supports basic OLAP operations. OLAP focuses on interactive data aggregation tools. – Data mining: • knowledge discovery from hidden patterns. tables.Data Warehouse Usage • Three kinds of data warehouse applications. – Analytical processing: • multidimensional analysis of data warehouse data. 50 . constructing analytical models. pivoting. slice-dice. charts and graphs. performing classification and prediction. and reporting using crosstabs.

• Architecture of OLAM (OLAP Mining): 51 . – OLAP-based exploratory data analysis • mining with drilling. Web accessing. – On-line selection of data mining functions. pivoting. • ODBC. – Available information processing structure surrounding data warehouses. reporting and OLAP tools. • DW contains integrated. dicing. cleaned data.From On-Line Analytical Processing to On Line Analytical Mining (OLAM) • Why online analytical mining? – High quality of data in data warehouses. consistent. • integration and swapping of multiple mining functions. algorithms. etc. service facilities. OLEDB. and tasks.

An OLAM Architecture (Layering) Mining query User GUI API Mining result Layer4 User Interface Layer3 OLAP/OLAM OLAM Engine Data Cube API OLAP Engine Layer2 MDDB Meta Data MDDB Filtering&Integration Databases Database API Data cleaning Filtering Data Warehouse Layer1 Data Repository 52 Data integration .

Summary • Data warehouse: – A subject-oriented. snowflake schema. – Multiway array aggregation. full vs. HOLAP. no materialization. integrated. dicing and pivoting. time-variant. MOLAP. • Efficient computation of data cubes: – Partial vs. • A multi-dimensional model of a data warehouse: – Star schema. rolling. 53 . • Further development of data cube technology: – Discovery-drive and multi-feature cubes. & nonvolatile collection of data in support of management’s decision-making process. – A data cube consists of dimensions & measures. – From OLAP to OLAM (on-line analytical mining). • OLAP operations: drilling. fact constellations. slicing. • OLAP servers: ROLAP. – Bitmap index and join index implementations.

R. Gupta. K. F. and S. Ramakrishnan. M. Abbadi. S. J. Venkatrao. Efficient view maintenance in data warehouses. Gray. 1999 ACM-SIGMOD. PA. Agrawal.olapcouncil. Deshpande. 417-427. 1997.References (I) • S. P. 506-521. 1997 ACM-SIGMOD. Gehrke. Bosworth. June 1999. S. Data cube: A relational aggregation operator generalizing group-by. J. Reichart. 1996 VLDB. Sarawagi. Chaudhuri. D.0. Sept. Modeling multidimensional databases. 1:29-54. April ‘97. In Proc. 1998 ACM SIGMOD. On the computation of multidimensional aggregates. Dayal. ACM SIGMOD Record. A. Conf. Washington. In Proc. An overview of data warehousing and OLAP technology. In Proc. Data Mining and Knowledge Discovery. 1996. A. June 1998. Naughton. In Proc. Chaudhuri and U. A. E. and H. 359-370. Sarawagi. 54 • • • • • • • . A. R. M. J. R. Agrawal. 1997 Int. Seattle. Arizona. Bottom-Up Computation of Sparse and Iceberg CUBEs. Automatic subspace clustering of high dimensional data for data mining applications. cross-tab and sub-totals. R. Raghavan. Singh. Pellow. Gunopulos. Pirahesh. Agarwal. 94-105. Ramakrishnan. 1997. England. Gupta. 1998. Yurek. Agrawal. Data Engineering. 26:65-74. Beyer and R. May 1997. A. India. and P. In Proc. and S. In http://www. Agrawal.htm. Bombay. OLAP council. F. Philadelphia. and T. A. 232-243. MDAPI specification version 2. Birmingham. D. D.

Srivastava. of Extending Database Technology (EDBT'98). Megiddo. and N. March 1998. March 1998. 1997 ACM-SIGMOD Int. Greece. Conf. R. Management of Data. of Extending Database Technology (EDBT'98). Rajaraman. OLEDB for OLAP programmer's reference version 1. In Proc. E. 1996 ACM-SIGMOD Int. Tucson. In Proc. Ullman.References (II) • V. Very Large Data Bases. May 1997. Spain. Implementing data cubes efficiently. Naughton.0. Aug. M. Sarawagi. Srivastava. In http://www. Agrawal. OLAP Solutions: Building Multidimensional Information Systems. Deshpande. Canada. Int. Management of Data. pages 168-182. Conf. Chatziantoniou. and D. John Wiley & Sons. P. D. S. In Proc. Conf. Conf. An array-based algorithm for simultaneous multidimensional aggregates. 1997 Int. D. 1998. Ross and D. Arizona. A. 159-170. K. 55 • • • • • • . In Proc. and J. Fast computation of sparse datacubes. 263-277. Y. and J. Montreal. 1997. Spain. Harinarayan. 1997. Zhao. pages Discovery-driven exploration of OLAP data cubes. Thomsen. Int. Complex aggregation at multiple granularities. Ross. Conf. In Proc. Microsoft. Valencia. June 1996. Valencia. K. 116-125. A. F.

Sign up to vote on this title
UsefulNot useful