Table partitioning is a data organization scheme in which table data is divided across multiple storage objects called data partitions.
In SAP HANA database, it is possible to split column-store tables horizontally into disjunctive sub-tables or partitions. The SAP HANA database supports several redistribution operations that use complex algorithms to evaluate the current distribution and determine a better distribution depending on the situation. Partitioning is typically used in distributed systems, but it may also be beneficial for single-host systems. Partitioning is transparent for SQL queries and data manipulation language statements.
In a distributed SAP HANA system, tables are assigned to an index server on a particular host at their time of creation, but this assignment can be changed. In certain situations, it is even necessary.
A non-partitioned table of SAP HANA database cannot store more than 2,000,000,000 (2 billion) rows.
For example, in SAP HANA side-by-side implementation, SLT will stop data replication when SAP HANA table reaches 2 billion records.
For simplicity, here I have discussed (with proper screen-shots) only Single-Level Partitioning with all the three partitioning specifications –
i) Hash, Range and Round-robin;
ii) I have shown the steps for re-distribution of all the partitions to different hosts in a distributed SAP HANA database;
iii) And how to change a partitioned table into a non-partitioned table also recorded here.