Presented by Russell Myers Paper by Ming-Chuan Wu and Alejandro P. Buchmann.

Slides:



Advertisements
Similar presentations
Bitmap Index Design and Evaluation Ariel Noy Data representation and retrieval seminar By: Chee-Yong Chan Yannis E.Ioannidis.
Advertisements

OLAP Tuning. Outline OLAP 101 – Data warehouse architecture – ROLAP, MOLAP and HOLAP Data Cube – Star Schema and operations – The CUBE operator – Tuning.
File Processing - Organizing file for Performance MVNC1 Organizing Files for Performance Chapter 6 Jim Skon.
Quick Review of Apr 10 material B+-Tree File Organization –similar to B+-tree index –leaf nodes store records, not pointers to records stored in an original.
Chapter 11 Indexing and Hashing (2) Yonsei University 2 nd Semester, 2013 Sanghyun Park.
File Processing : Hash 2015, Spring Pusan National University Ki-Joune Li.
©Silberschatz, Korth and Sudarshan12.1Database System Concepts Chapter 12: Indexing and Hashing Basic Concepts Ordered Indices B+-Tree Index Files B-Tree.
Management Information Systems, Sixth Edition
Topic Denormalisation S McKeever Advanced Databases 1.
BTrees & Bitmap Indexes
Chapter 3 Database Management
Physical Database Design CIT alternate keys - named constraints - indexes.
Organizing Data & Information
Chapter 3: Data Storage and Access Methods
It refers to the software used to manage the database.
IST Databases and DBMSs Todd S. Bacastow January 2005.
Cloud Computing Lecture Column Store – alternative organization for big relational data.
File Organization Techniques
1 DATABASE TECHNOLOGIES BUS Abdou Illia, Fall 2007 (Week 3, Tuesday 9/4/2007)
Naming and Directories. Recall from the last time… File system components Disk management organizes disk blocks into files. Many disk blocks management.
Systems analysis and design, 6th edition Dennis, wixom, and roth
CSC271 Database Systems Lecture # 30.
IT The Relational DBMS Section 06. Relational Database Theory Physical Database Design.
Oracle Data Block Oracle Concepts Manual. Oracle Rows Oracle Concepts Manual.
1 © Prentice Hall, 2002 Physical Database Design Dr. Bijoy Bordoloi.
 A databases is a collection of data organized to make it easy to search and easy to retrieve in a useful, usable form.
1 California State University, Fullerton Chapter 7 Information System Data Management.
CS 345: Topics in Data Warehousing Tuesday, October 19, 2004.
Physical Database Design & Performance. Optimizing for Query Performance For DBs with high retrieval traffic as compared to maintenance traffic, optimizing.
TM 7-1 Copyright © 1999 Addison Wesley Longman, Inc. Physical Database Design.
Physical Database Design Chapter 6. Physical Design and implementation 1.Translate global logical data model for target DBMS  1.1Design base relations.
Chapter 6 1 © Prentice Hall, 2002 The Physical Design Stage of SDLC (figures 2.4, 2.5 revisited) Project Identification and Selection Project Initiation.
Information Systems Today (©2006 Prentice Hall) 3-1 CS3754 Class Note 12 Summery of Relational Database.
I Information Systems Technology Ross Malaga 4 "Part I Understanding Information Systems Technology" Copyright © 2005 Prentice Hall, Inc. 4-1 DATABASE.
MULTIMEDIA DATABASES -Define data -Define databases.
Data Warehouse Design Xintao Wu University of North Carolina at Charlotte Nov 10, 2008.
The Simigle Image Search Engine Wei Dong
IS 325 Notes for Wednesday August 28, Data is the Core of the Enterprise.
ITGS Databases.
1 Biometric Databases. 2 Overview Problems associated with Biometric databases Some practical solutions Some existing DBMS.
GIS Data Models GEOG 370 Christine Erlien, Instructor.
Building Dashboards SharePoint and Business Intelligence.
Database Indexing 1 After this lecture, you should be able to:  Understand why we need database indexing.  Define indexes for your tables in MySQL. 
Variant Indexes. Specialized Indexes? Data warehouses are large databases with data integrated from many independent sources. Queries are often complex.
Physical Database Design Purpose- translate the logical description of data into the technical specifications for storing and retrieving data Goal - create.
1 Lecture 21: Hash Tables Wednesday, November 17, 2004.
Chapter 8 Physical Database Design. Outline Overview of Physical Database Design Inputs of Physical Database Design File Structures Query Optimization.
Query Optimization CMPE 226 Database Systems By, Arjun Gangisetty
© 2003 Prentice Hall, Inc.3-1 Chapter 3 Database Management Information Systems Today Leonard Jessup and Joseph Valacich.
Last Updated : 27 th April 2004 Center of Excellence Data Warehousing Group Teradata Performance Optimization.
Indexing OLAP Data Sunita Sarawagi Monowar Hossain York University.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Data Warehousing and Decision Support Chapter 25.
Column Oriented Database By: Deepak Sood Garima Chhikara Neha Rani Vijayita Gumber.
Management Information Systems by Prof. Park Kyung-Hye Chapter 7 (8th Week) Databases and Data Warehouses 07.
Databases and DBMSs Todd S. Bacastow January
Indexing Structures for Files and Physical Database Design
Index An index is a performance-tuning method of allowing faster retrieval of records. An index creates an entry for each value that appears in the indexed.
Indexing Goals: Store large files Support multiple search keys
Storage and Indexes Chapter 8 & 9
Informix Red Brick Warehouse 5.1
Database Performance Tuning and Query Optimization
Basic Concepts in Data Management
Physical Database Design
View and Index Selection Problem in Data Warehousing Environments
2018, Spring Pusan National University Ki-Joune Li
Chapter 11 Database Performance Tuning and Query Optimization
Chapter 3 Database Management
Unit 12 Index in Database 大量資料存取方法之研究 Approaches to Access/Store Large Data 楊維邦 博士 國立東華大學 資訊管理系教授.
Presentation transcript:

Presented by Russell Myers Paper by Ming-Chuan Wu and Alejandro P. Buchmann

Problem  Optimizations and tuning designed for On-Line Transaction Processing rather than Data Warehouses  Data Warehouses have specific needs Complex queries Huge volume of data returned as well as updated  Database systems generally not built for image data

Data Warehousing  How do we retrieve data efficiently based on various metrics? Represented as a portion of the tuple Represented in metrics tables Represented as a defined data range (e.g. bitmaps)

Tuple-based  Including the metrics directly in the tuple Hard to index based on and search through Not easily updated and costs a lot of storage space (e.g. have to insert new metrics for every tuple) Traverse in linear time

Metrics Tables  Data could be represented in associative metrics tables Less data to store – just associations and the metric data Quicker search – follow the metric to all the primary keys of the individual pieces of data Still linear

Bitmapping  Each tuple contains a small portion of encoded bitmap data Can organize the bitmap into decision trees and use to search – less time Insertion and amount of data is lessened Slice the data into various portions to represent multiple metrics and search through those

Encoding Techniques  Hierarchical encoding Ex: Region to district to store  Range Eliminate searching from things outside of a range (e.g. searching between 10 and 13 and excluding all others)  Ordering

The Paper  The paper seeks to prove that bitmapping techniques are the way to go  Performance analysis of various bitmapping techniques  Proofs of operations times

Critique  Excellent start Explained the topic clearly Made the basis of the paper easy to understand  Confounding expansion Confused by direction Differences between various bitmap techniques?

Critique  Bit slicing  Mapping techniques  Representations of bitmaps  Metric graphical representation  Advantages to different encoding techniques

Contributions  Bitmap indexing and tree structures bring faster data results Much cleaner than alternative means Easily represented Mapping situations are smaller than representing each piece of data