1. Column-Oriented Database Yiqun Xie (Ian) & Yingbin Liang (Ben) Group 9

2. Row-based RDBMS vs. Column-oriented DBMS

3. Row-based, the best solution? Big Data OLAP-Online Analytical Processing … …

4. Traditional row-based RDBMS Optimal write time and abundant reading overhead for retrieval of subset queries Traversing all the headers! Going through all attributes. varchar

5. From row to column… SELECT c1 FROM bigtable; … … ideal

6. Column-oriented DBMS Optimal read time for subset retrieval queries SELECT c1 FROM bigtable; 100GB 1GB 10GB 20GB 19GB 30GB 20GB col6 col1 col2 col3 col4 col5 RDBMS Strengths

7. SQL Example: SELECT month, store FROM sales, products WHERE productType = ‘technology’ AND products.id = sales.productID GROUP BY month, store Easier to implement data compression algorithms (e.g. Run-length encoding) Only read columns needed ! (7 columns) Fruit (3 Apples, 2 Pears, 1 Banana, 2 Oranges, 1 Apple)

8. Column-oriented DBMS Bad write performance Advanced column-oriented storage system: HBase, MongoDB, MapReduce INSERT INTO bigtable VALUES (Rn1, Rn2, Rn3, Rn4) Weakness

9. Relationship With Course

10. References [1] http://www.cs.yale.edu/homes/dna/talks/Column_Store_Tutorial _VLDB09.pdf [2] http://www.spatial.cs.umn.edu/Courses/Fall11/5707/class_no tes/G5.ppt [3] http://www.slideshare.net/arangodb/introduction-to-column- oriented-databases [4] Column-oriented database speeds predictive criminal monitoring program

11. Questions?