1. Columnar Database Systems
Source: Query Execution in Column-Oriented Database Systems
Daniel J. Abadi
Presented by – Sandeep Ummadi & Uday Kumar Raju

2. Motivation & Summary Class News –
“Teradata Upgrades Break Down Database Barriers” – Information week – 22,Sept, 2011
Big Data
Summary –
Columnar Databases
RDBMS vs. Columnar Oriented DBMS
Advantages

3. Columnar Database Systems[1]
Stores content by columns rather than row.
The 2-D data represented at conceptual level will be mapped to 1-D data structure at physical level.
Row-by –Row approach keeps all the information about one entity together.
Column – by –Column approach keeps all attribute information together.
Column oriented databases handle fixed length data
Source: VLDB Tutorial 2009 – Column Oriented Database Systems - Stavros Harizopoulos, Daniel Abadi, Peter Boncz

4. RDBMS vs. Columnar Oriented DBMS (Logical Level )
Columnar DBMS are special purpose databases and are not designed to replace general purpose RDBMS.
Logical storing details of RDBMS vs. Columnar DBMS.
Pic Source: VLDB Tutorial 2009 – Column Oriented Database Systems - Stavros Harizopoulos, Daniel Abadi, Peter Boncz

5. RDBMS vs. Columnar Oriented DBMS (Physical Level )
Column oriented
Row oriented

6. Query Execution ( Row oriented)
Select * from Employee_database;

7. Query Execution
Select * from Employee_database;

8. Query Execution
Select * from Employee_database;

9. Why Column Oriented Database?
Most data warehousing applications make more number of reads and lesser number of writes.
They mostly retrieve and analyze lesser number of columns compare to the several number of columns that actually exist.
Row oriented databases have the overhead of seeking through all columns.
Row oriented data warehouses still persistent.

10. Query Execution ( Columnar Databases)
Select count(E.id) from Employee_Database E;

11. Query Execution ( Columnar Databases)
Select count(E.id) from Employee_Database E; id
salary
Emp_ssn
dateOfBirth

12. Tradeoffs
Row oriented databases work well for granularity at the entity level.
Column oriented databases work well for granularity at the attribute level.
Row oriented – Optimal write time and abundant reading overhead for retrieval of subset queries.
Column oriented – Optimal read time for subset retrieval queries, bad write performance.

13. Applications
Majorly applicable for Data warehouses and Business Intelligence– Required more analytical processing rather transaction processing ( Read More and Write Less).
Online Analytical Processing ( At the attribute level )
Decision making
Analyzing unorganized BIG DATA with improved granularity
Data Marts development
Data Mining
Latest – Assistance to law enforcement agency, SecureAlert

14. Industry Role Teradata Vertica Sybase SAND CDBMS Sybase IQ
Aster Data Systems, etc..

15. References [1] http://en.wikipedia.org/wiki/Column-oriented_DBMS
[2]
[3] MIT Columnar Oriented data base tutorial
[4] VLDB 09 – Column Oriented Data Base.
[5] Query Execution in Column-Oriented Database Systems - Daniel J. Abadi – PhD Dissertation.
[6]

16. Queries?

17. Thank You