SAP HANA Sizing and Approaches

SAP HANA Sizing

• SAP HANA sizing focuses primarily on the main memory needed to hold the data.
• The exact memory requirement depends on the scenario and cannot be estimated directly from source database size.
• A Quick Sizer tool or SAP HANA sizing reports are necessary to determine the required memory.
• SAP HANA compresses data in memory, affecting memory calculation.

Sizing Approaches

• Customers new to SAP applications and HANA often use the Quick Sizer.
• Existing SAP customers migrating to HANA use sizing reports to determine the required memory.
• Complex implementations, such as consolidating multiple ERP systems or migrating high-volume legacy systems, require expert sizing.
• Different scenarios (New implementation, Database migration) use different approaches to estimate sizes.

SAP HANA Tailored Data Center Integration (TDI)

• TDI allows greater flexibility in hardware choices compared to using only SAP HANA appliances.
• TDI enables reusing existing hardware, reducing hardware and operational costs.
• TDI offers more flexibility in hardware vendor selection, leveraging existing IT management processes.
• SAP does not offer formal certification for TDI infrastructure. Instead, SAP certifies hardware components.
• Customer must meet the requirements dictated by SAP HANA.

DRAM Sizing

• The first step is memory sizing, using a Quick Sizer tool or SAP Notes.
• Varying use cases dictate different resources for sizing.
• Memory sizing reports from SAP notes should be used, in addition to the Quick Sizer.
• The reports listed are examples and should be consulted when implementing SAP HANA.
• Both quick sizer input and the information found in reports are necessary to ensure accurate sizing.

Disk Sizing

• The data volume size is crucial for sizing.
• The log volume space is based on data changes between savepoints, crucial for recovery.
• The data volume requires approximately 20% extra space for delta merge operations and growth.

Backup Considerations

• Backup cycles consider full backups (weekends) and incremental backups (workdays).
• The necessary space depends on the backup strategy (all full backups, weekend full backups, workdays incremental backups)

Network Requirements

• Database sizing takes into account the size of the network and network components.
• SAP HANA appliances often include the internal and storage network, while client and admin zones are typically customer responsibility.
• The network's capacity for internal and storage zones must meet minimum requirements.

CPU Sizing

• CPU sizing is calculated based on throughput needed for query complexity.
• CPU needs are calculated based on the number of concurrent users and the complexity of queries.
• 300 SAPS per active user with a 65% buffer are the recommended minimum CPU capacity.

Sizing Method Quick Sizer

• The Quick Sizer tool is utilized for initial hardware sizing.
• Multiple predefined scenarios (e.g., SAP Business Suite, SAP S/4HANA, SAP BW/4HANA) can be used for initial estimations.
• The tool calculates CPU, disk, and memory requirements.
• The input needed will be determined by the customers current setup.

SAP HANA Appliance Sizing

• Hardware installation sizing should be done utilizing the Quick Sizer.
• Information included in SAP notes should be used in conjunction with the Quick Sizer calculations.
• The factors in the sizing may vary depending on the application being migrated to HANA.