Main memory capacity is always a fascinating issue for SAP HANA and data warehouse scenarios when compared with ERP applications, or applications with relatively steady volumes of data. There is one key point to remember: make sure that you never run out of main memory space.
The good performance of a HANA database stems from the systematic orientation to an in-memory database, as well as using modern compression and Columnstore algorithms. This means that the database has to read comparatively less data when calculating aggregations for large quantities of data and can also perform this task exceptionally quickly even in the central memory.
However, one of these benefits may very quickly be rendered moot if the design of the data model is below par. As such, major benefits in terms of runtime and agility may become null and void for both the HANA database, as well as the users.
Having tested Exasol's "lift and shift" migration approach, b.telligent consultant Simon explains step by step how to migrate to the cloud with confidence
In order to ensure performant reporting based on SAP BW, it is necessary to avoid redundant requests. An important element in this context is the optimized master data request. This can be implemented particularly easily and effectively for hierarchy objects (especially menu hierarchies).
When working with arcplan, there are different methods to generate a list without duplicates from a list of data with double entries. In many cases, a database consultation grouped accordingly may perform this task. Time and again, however, there are cases in which it is necessary to remove the duplicates with the assistance of arcplan functions.
When a BW system uses an SAP HANA database, it is possible to use what are called „Mixed Scenarios“. In these scenarios you can use SAP HANA tools to combine data modeled in both the BW system and in SAP HANA.
