Sizing of SAP HANA
The actual memory requirement of SAP HANA is depend on operational conditions which can be considered only by analyzing the HANA system. SAP certified HANA hardware configurations are available at HANA Product Availability Matrix. In 2010 the biggest HANA hardware configuration available was 2TB of memory with 512GB per node. At SAPPHIRE 2012, hardware partners presented a 16 node HANA system with 16TB Memory with 1TB per node. SAP showcased at SAPPHIRE 2012 a custom HANA system running 4000 cores with 100TB of Memory.
1.1 Sizing of SAP HANA
SAP HANA In-Memory Database sizing consists of Memory sizing for static data, Memory sizing for objects created during runtime (data load and query execution), Disk Sizing and CPU Sizing.
Memory sizing for static data: Memory requirements for static data are derived from the database footprint of the corresponding tables of the source database system.
Memory sizing for objects created during runtime (data load and query execution): Additional memory required for objects that are created dynamically when loading new data and while executing queries.
Disk Sizing: Disk sizing for persistence layer and for log files / operational disk space.
CPU Sizing: Sizing approach similar to user based CPU sizing of BW and BWA.
SAP note: 1514966- SAP HANA 1.0: Sizing SAP In Memory database details the sizing requirements of SAP In-memory database.
1.2 Sizing of SAP BW on HANA
SAP BW on HANA sizing consists of memory sizing, disk sizing and CPU sizing.
Memory Sizing: Memory for column store, Memory for row store and Memory for caches and additional components.
Disk Sizing: Disk sizing for data files and Disk sizing for log files and CPU sizing.
Sap Note: 1637145- SAP BW on HANA: Sizing SAP in-Memory database details the sizing requirements for SAP BW on HANA. SAP note: 1736976: Sizing Report for BW on HANA has a sizing report, report /SDF/HANA_BW_SIZING which is a replacement of the database dependent sizing scripts provided in SAP note 1637145.