What is HANA A SAP High-Performance Analytic Appliance (HANA) is a data warehouse appliance for processing high volumes of operational

and transactional data in real-time. HANA uses in-memory analytics, an approach that queries data stored in random access memory (RAM) instead of on hard disk or flash storage. A HANA appliance uses an SAP Sybase replication server to copy and synchronize data from an SAP data warehouse or enterprise resource planning (ERP) application in real-time. By running in parallel to the source SAP ERP application, HANA allows business users to query large volumes of data in real-time without having to wait for scheduled reports to run. HANA supports industry standards such as structured query language (SQL) and multi-dimensional eXpressions (MDX). It also includes a programming component that allows a company's IT department to create and run customized applications on top of HANA. ......

Column Store

Improves read functionality significantly, also improves write functionality Highly compressed data No real files, virtual files Optimizer and Executer Handles queries and execution plan Delta data for fast write Asynchronous delta merge Consistent view Manager Main store compressed and read optimized Data is read from Main Store Delta Store Write optimized for write operations. Asynchronous merge move the data from delta store to main store Compression by create dictionary and applying further compression methods Even during the merge operation, the columnar table will still be available for read and write operations. To fulfil this, a second delta and main storage are used internally Merge operation can also be triggered manually with an SQL command Column stores, such as HPs Vertica or SAP Sybase IQ, store data by column. By contrast, traditional SQL databases store data as rows. The benefit of storing data as rows is that it is often the fastest way to look up a single value, such as salary, given a key value like the employee ID. Columnar databases group data by column. Within a column, generally speaking, all the data is of the same type. A columnar store, therefore, stores data of a single type all together, which can give advantages such as the possibility for significant compression. Good compression can lead to reduced disk space requirements, memory requirements, and access times. ......

ROW Store

One of the relational engines to store data in row format. o Pure in-memory store (Future versions will also have an option of disk based store) o In memory object store (in future) for live cache functionality o Transactions Version Memory is the heart of row store Row store architecture o Write operation mainly go into "Transactional Version Memory" o INSERT also writes to persisted segment o Moves visible version from memory to persisted segment o Clears outdated record versions from Transactional Version memory o Row Store tables have a primary index o Row ID maps to primary key o Secondary indexes can be created o Row ID contains the segment and the page for the record o Indexes in row store only exist in memory o Index definition stored with table meta ......