Collected information regarding partitioning in SAP HANA (with examples)

last updated: 2023-03-17

Introduction

There is huge knowledge available about SAP HANA partitioning, but the knowledge is very fragmented (Help Portal, Blog post, SAP KBA, SAP Note, other). In order to simply and make content consumption easier I have created a centralized page, a single source of the available information regarding SAP HANA partitioning. Further I would like to help you with partitioning exercises in SAP HANA, express edition to demonstrate the process.

Table of Content

1. Task 1. – Exercise
   1. Prerequisites
   2. Background
   3. Exercise 1. – Partitioning “SBOOK” table (HASH, single-level)
   4. Exercise 2. – Increase the total number of partitions in “SBOOK” table (HASH, single-level)
   5. Exercise 3. – Partitioning “SBOOK” table (RANGE, single-level)
   6. Exercise 4./A. – Adding new RANGE partition (RANGE, single-level)
   7. Exercise 4./B. – Dropping specific RANGE partition (RANGE, single-level)
   8. Exercise 5. – Partitioning “SBOOK” table (HASH / HASH, multi-level)
   9. Exercise 6. – Increase the total number of partitions in “SBOOK” table (HASH / HASH, multi-level)
   10. Exercise 7. – Partitioning “SBOOK” table (HASH / RANGE, multi-level)
   11. Exercise 8. – Adding new RANGE partition (HASH / RANGE, multi-level)
   12. Exercise 9. – Partitioning “SBOOK” table (RANGE / RANGE, multi-level)
   13. Exercise 10. – Adding new RANGE partition on the first level into a multi-level-partitioned table (RANGE / RANGE, multi-level)
   14. Exercise +1. – Merge partitions (partitioned table to non-partitioned)
   15. Conclusion
2. Task 2. – Documentation Library
   1. Where to find documentations in SAP Help Portal?
   2. Which is the master SAP Knowledge Base Article of the SAP HANA partitioning?
   3. Before Partitioning
   4. Which best practices are available regarding SAP HANA partitioning?
   5. Which other documentation is important regarding SAP HANA partitioning?
   6. Which SAP HANA Alert IDs belongs to the partitioning topic?
   7. What are the available tools for partitioning?
   8. What are the known issues?
   9. What blog posts can be helpful?
   10. Other articles in this series
   11. Other articles in connected series
   12. Useful bookmark
3. Task 3. – Use Cases
4. Task 4. – Recommendation / Best Practice / Consideration

Task 1. – Exercise

Prerequisites

• Hypervisor (VMware Workstation Player 16)
• SAP HANA, express edition (db version: 2.00.061)
  Install SAP HANA 2.0, express edition on a Preconfigured Virtual Machine (with SAP HANA XS Advanced)
• SAP HANA Studio (version: 2.3.63)

Background

During the exercises I will use test database SFLIGHT. More information can be find:
SAP HANA, express edition and SFLIGHT demo database, modeling – Complete Tutorial

The SFLIGHT schema is in the Catalog folder.

Exercise 1. – Partitioning “SBOOK” table (HASH, single-level)

Checking how much data can be found in the table.

SELECT COUNT(*) FROM "SFLIGHT"."SBOOK"

In production system the amount of data (~1 million row) should not be partitioned. It will be partitioned to demonstrate the process (test system).

Checking the data itself.

SELECT TOP 1000 * FROM "SFLIGHT"."SBOOK" ORDER BY "BOOKID"

“BOOKID” column seems to be a good choice for HASH partitioning.

ALTER TABLE "SFLIGHT"."SBOOK" PARTITION BY HASH ("BOOKID") PARTITIONS 2;

The partitioning was successful and the data distribution is also perfect.

Exercise 2. – Increase the total number of partitions in “SBOOK” table (HASH, single-level)

Re-partition the table with 4 partition. Multiply the actual partition number 2 => 4!

ALTER TABLE "SFLIGHT"."SBOOK" PARTITION BY HASH ("BOOKID") PARTITIONS 4;

The partitioning was successful and the data distribution is also perfect.

Exercise 3. – Partitioning “SBOOK” table (RANGE, single-level)

Checking the data itself.

SELECT DISTINCT "FLDATE" FROM "SFLIGHT"."SBOOK" ORDER BY "FLDATE"

“FLDATE” column seems to be a good choice for RANGE partitioning.

Partition/re-partition the table to be a single-level partitioned table.

ALTER TABLE "SFLIGHT"."SBOOK" PARTITION BY 
RANGE ("FLDATE") 
(PARTITION 20100101 <= VALUES < 20110101, 
 PARTITION 20110101 <= VALUES < 20120101,
 PARTITION 20120101 <= VALUES < 20130101,
 PARTITION OTHERS
);

Exercise 4./A. – Adding new RANGE partition (RANGE, single-level)

Adding new RANGE partition to an already single-level partitioned table.

ALTER TABLE "SFLIGHT"."SBOOK" ADD PARTITION 19900101 <= VALUES < 20100101;

❗Remark: The records (18) were moved to the new partition (where belongs to) from the OTHERS partition.

Exercise 4./B. – Dropping specific RANGE partition (RANGE, single-level)

Dropping specific RANGE partition from a single-level partitioned table.

ALTER TABLE "SFLIGHT"."SBOOK" DROP PARTITION 19900101 <= VALUES < 20100101;

❗WARNING: Dropping the partition won’t move the data back to the OTHERS partition. All data is deleted when dropping a partition.

SAP HANA Dynamic Tiering: Administration Guide – Drop a Partition

Exercise 5. – Partitioning “SBOOK” table (HASH / HASH, multi-level)

Partition/re-partition the table to be a multi-level partitioned table.

ALTER TABLE "SFLIGHT"."SBOOK" PARTITION BY 
HASH ("BOOKID") PARTITIONS 2, 
HASH ("CUSTOMID") PARTITIONS 2;

The partitioning was successful and the data distribution is also perfect.

❗Remark: Scenario had been tested in case of performance perspective.

⌛- – > Performance results (HASH 2 BOOKID; HASH 2 CUSTOMID): ~ 1.5 seconds

Exercise 6. – Increase the total number of partitions in “SBOOK” table (HASH / HASH, multi-level)

Re-partition the table with 4 partition (on second level). Multiply the actual partition number 2 => 4!

ALTER TABLE "SFLIGHT"."SBOOK" PARTITION BY 
HASH ("BOOKID") PARTITIONS 2, 
HASH ("CUSTOMID") PARTITIONS 4;

The partitioning was successful and the data distribution is also perfect.

❗Remark: Scenario had been tested in case of performance perspective. (multiple / divider rule)

⌛- – > Performance results (HASH 2 BOOKID; HASH 4 CUSTOMID): ~ 1.0 seconds
⌛- – > Performance results (HASH 2 BOOKID; HASH 3 CUSTOMID): ~ 4.0 seconds !!!!!

Exercise 7. – Partitioning “SBOOK” table (HASH / RANGE, multi-level)

Partition/re-partition the table to be a multi-level partitioned table.

ALTER TABLE "SFLIGHT"."SBOOK" PARTITION BY 
HASH ("BOOKID") PARTITIONS 2, 
RANGE ("FLDATE") 
(PARTITION 20100101 <= VALUES < 20110101, 
 PARTITION 20110101 <= VALUES < 20120101,
 PARTITION 20120101 <= VALUES < 20130101,
 PARTITION OTHERS
);

Exercise 8. – Adding new RANGE partition (HASH / RANGE, multi-level)

Adding new RANGE partition to an already multi-level partitioned table.

ALTER TABLE "SFLIGHT"."SBOOK" ADD PARTITION ("FLDATE") 19900101 <= VALUES < 20100101;

Exercise 9. – Partitioning “SBOOK” table (RANGE / RANGE, multi-level)

To be able to do the task, we need to modify the database table slightly. We create a copy from the original table.

-- table copy

CREATE COLUMN TABLE "SFLIGHT"."SBOOK_COPY" LIKE "SFLIGHT"."SBOOK" WITH DATA;

-- create new columns

ALTER TABLE "SFLIGHT"."SBOOK_COPY" ADD (FLDATE_YEAR NVARCHAR(4));
ALTER TABLE "SFLIGHT"."SBOOK_COPY" ADD (FLDATE_MONTH NVARCHAR(2));
ALTER TABLE "SFLIGHT"."SBOOK_COPY" ADD (FLDATE_DAY NVARCHAR(2));

-- update new columns content based on FLDATE column

UPDATE "SFLIGHT"."SBOOK_COPY" SET FLDATE_YEAR = YEAR(FLDATE);
UPDATE "SFLIGHT"."SBOOK_COPY" SET FLDATE_MONTH = MONTH(FLDATE);

-- recreate primary key (to be able to use FLDATE_YEAR column as a first level partitioning column)

ALTER TABLE "SFLIGHT"."SBOOK_COPY" DROP PRIMARY KEY;
ALTER TABLE "SFLIGHT"."SBOOK_COPY" ADD PRIMARY KEY (MANDT,CARRID,CONNID,FLDATE,BOOKID,FLDATE_YEAR);

After the modification the partitioning action can be done.

ALTER TABLE "SFLIGHT"."SBOOK_COPY" PARTITION BY 
RANGE (FLDATE_YEAR) 
(PARTITION VALUE = 2010, 
 PARTITION VALUE = 2011,
 PARTITION VALUE = 2012,
 PARTITION OTHERS), 
RANGE (FLDATE_MONTH) 
(PARTITION 01 <= VALUES < 07,
 PARTITION 07 <= VALUES < 13,
 PARTITION OTHERS);

Exercise 10. – Adding new RANGE partition on the first level into a multi-level-partitioned table (RANGE / RANGE, multi-level)

ALTER TABLE "SFLIGHT"."SBOOK_COPY" ADD PARTITION (FLDATE_YEAR) value = 1995;

Exercise +1. – Merge partitions (partitioned table to non-partitioned)

Merging the partitions results the table into the initial state (non-partitioned).

ALTER TABLE "SFLIGHT"."SBOOK" MERGE PARTITIONS

Conclusion

Partitioning/re-partitioning is an easy task in case of SAP HANA. The only important part is the syntax which you need to use correctly. Of course in a huge database the process will be time and resource consuming.

Task 2. – Documentation Library

IMPORTANT !
=================================================================

Where to find documentations in SAP Help Portal?

• SAP HANA Administration Guide for SAP HANA Platform – Table Partitioning
• SAP HANA SQL Reference Guide for SAP HANA Platform – ALTER TABLE Statement (Data Definition)

Which is the master SAP Knowledge Base Article of the SAP HANA partitioning?

• 2044468 – FAQ: SAP HANA Partitioning

=================================================================

Before partitioning

Take into consideration that partitioning is not always necessary / not the only option (data deletion and / or archiving). Also housekeeping activity should be done before partitioning.

• 2388483 – How-To: Data Management for Technical Tables
• 2400024 – How-To: SAP HANA Administration and Monitoring
• 2718597 – Collection solutions for some big growth tables relevant to HANA DB
• 2772795 – Recommendations to reduce the size of a table or partition where SAP HANA is the Database

Which best practices are available regarding SAP HANA partitioning?

• 3199581 – Advantages of HANA Partitioning
• 2289491 – Best Practices for Partitioning of Finance Tables
• 2874176 – Parameter Recommendations for Online Table Operations
• 2418299 – SAP HANA: Partitioning Best Practices / Examples for SAP Tables
• 3146645 – What is the best approach in partitioning tables on SAP HANA?

Which other documentation is important regarding SAP HANA partitioning?

• 3234063 – How to partition/re-partition a table
• 2949496 – Add partition in HASH-RANGE partition
• 3198529 – Supported combination of multi-level Partitioning
• 3260918 – HANA: What are the main repartitioning phases?
• 2938647 – How many levels partition are supported by HANA
• 2444769 – Hana partitioning of a existing table with ROUND ROBIN
• 2942131 – How to check the progress of an ongoing partitioning activity?
• 3215774 – Monitor and troubleshoot for a long process of table repartition
• 2902172 – How to remove or re-create SAP HANA Database table partition
• 3215782 – How to perform Table partition or redistribution from HANA Cockpit
• 3289845 – SAP systems restart requirements after SAP HANA table partitioning
• 3288401 – How to find information about actual table partitioning in SAP HANA?
• 3214124 – How to estimate how much extra space is needed for a table partition
• 3111531 – SAP HANA – How to convert an existing hash partitioned table to range
• 3029040 – Add a new range partition on the first level into a multi-level-partitioned table
• 3314152 – Are there performance and resource related parameters for SAP HANA table partitioning?
• 2698617 – How to increase the total number of partitions of an already hash partitioned table in SAP HANA
• 2952826 – Perform table partitioning on HANA primary site requires additional steps on secondary site?
• 3307500 – How to decide which partitioning type and column(s) should been used to partition a table in SAP HANA?
• 3313721 – How to split/break a specific RANGE partition in already partitioned table which contains data in SAP HANA?
• 3225157 – /hana/data & hana/log volumes consumption reaches critical size post re-partitioning operations on a large table

Which SAP HANA Alert IDs belongs to the partitioning topic?

• 2445867 – How-To: Interpreting and Resolving SAP HANA Alerts
• 1909763 – How to handle HANA Alert 17: ‘Record count of non-partitioned column-store tables’
• 1910140 – How to Handle Alert 20 ‘Table growth of non-partitioned column-store tables’
• 1910188 – How to handle HANA Alert 27: ‘Record count of column-store table partitions’

What are the available tools for partitioning?

The general way to do partitioning/re-partitioning is to use SQL commands. The action can be done in a graphical way also.

• SAP HANA Administration with SAP HANA Studio – Partition a Non-Partitioned Table
• SAP HANA Administration with SAP HANA Cockpit – Partition a Table

What are the known issues?

• 3157330 – Memory allocation failed during (re-)partitioning
• 2994267 – HANA DB partitioning is failing with out of memory error
• 2890332 – Table re-partitioning failed with error “Data receive failed”
• 3281773 – What cause the non uniform data distribution in HASH partitioned table in SAP HANA?
• 3193321 – Partitioning or Re-Partitioning Job is running for a long time due to redo log contention that blocks Savepoint

What blog posts can be helpful?

• Table partition in HANA
• Various Table Partitioning Options in SAP HANA
• SQL & CDS Table Partitioning the graphical way
• How to determine and perform SAP HANA partitioning
• HANA Partitioning – 2 billion rows limitation – Part I: BWoH / BW/4HANA
• HANA Partitioning – 2 billion rows limitation – Part II: BSoH / S/4HANA

Other articles in this series

✍️ Collected information about memory in context of SAP HANA

✍️ Collected information regarding High Availability and Disaster Recovery in SAP HANA

✍️ Collected information about reclaim / shrink / defragmentation topic in context of SAP HANA persistence (with example)

Other articles in connected series

✍️ Where can I find knowledge and information belongs to SAP HANA?

Useful bookmark

🔖 2872774 – Bookmark of Frequently Asked Questions for SAP HANA

Task 3. – Use Cases

Few examples about how documentations belongs to each other and how to use them in an effective way.

Task 4. – Recommendation / Best Practice / Consideration

Few general information and recommendation which can be useful.

Do you have further questions?

Q&A link for SAP HANA: https://answers.sap.com/tags/73554900100700000996

Contribution

If you find any missing information belongs to the topic, please let me know. I am happy to add the new content. My intention is to maintain the content continuously to keep the info up-to-date.

Release Information