The preface
We can focus on my public number, the number public in the layout better, read more comfortable.
Body part
SAP HANA handle a large number of fast data speeds that understands
1: Data Management Optimization data stored using the column access HANA
To read columns from a database table, others ignored
2: For the access speed between the CPU and the memory, increasing the core, the compressed data
3: using a column technique efficient use of the CPU memory cache.
It reads the data stored in rows likely to cause loss of data read and cache memory
4: jacket reading technique using the new CPU data is pre-read
A cache data is read while the other read-ahead cache data.
HANA uses the ranks of hybrid storage mode
I.e., a single database system supports two different data storage mode.
Traditionally database table is a two-dimensional table consists of rows and columns.
Line data storage contains a record of all
The way the column stores all the data contained in this column.
The following presentation:
Such a database table, then,
Line storage as follows:
Column storage as follows:
It is generally believed that stores read data columns than rows of storage
Updates to the data stored in the line better.
Therefore, a column store for the following situations:
1: statistical computing and access large amounts of data will be needed in a few single accessible
2: For the case where the table structure requires frequent changes or extensions
3: many rows and columns of field operations frequently
4: When the main column, there are many cases of duplicate data, the data can be compressed
Line storage for use in the following situations:
1: At some point in time to record only a single line of treatment.
2: all columns need access to this information recording avoid leaping read access.
3: column contains main data will not be repeated.
4: There is no need for the rapid polymerization or quick query.
5: records in a database table without too many cases.
More, I am concerned about the number of public right.