If you are an experienced ABAP Developer, then you most likely know the classical performance guidelines for using Open SQL (if not, then you should look them up immediately).
One of the frequently asked questions we receive is:
“What changes in the context of SAP HANA regarding these guidelines?”
Let us first reconsider the existing guidelines. In a nutshell, they are usually summarized in the “5 golden rules”:
Well, the short answer regarding the question above is
- All existing (standard and custom) ABAP code runs on SAP HANA without modifications
- All the existing guidelines are still valid for SAP HANA as general recommendation
However, the priorities of some rules are changing, i.e. some aspects are less important due to the nature of the In-Memory Column Store but there are also certain patterns of non-optimal coding with higher impact on SAP HANA. Furthermore, there are completely new opportunities for performance tuning on SAP HANA which were not possible in the past, e.g. by pushing complex operations to the database.
In this blog series, Hermann Gahm and myself will drill into more details of the slightly adapted performance recommendations, and give some background information. In addition, we try to give some guidance for several frequently asked questions.
The planned structure of this blog series is as follows:
- Performance Guidelines for ABAP Development on the SAP HANA Database (this post)
- Details and background information on adapted guidelines (to come)
- Frequently Asked Questions for ABAP Development on SAP HANA (to come)
The following recommendations are derived from measurements and experiences based on SAP Business Suite using SAP NetWeaver AS ABAP 7.4 running on SAP HANA SPS5. They will be added to the standard ABAP 7.4 documentation and also supported in standard tools such as the ABAP code inspector.
As outlined above, the next post contains some more technical background information for the reasoning behind these recommendations, and some answers to frequently asked questions.