SAP HANA Sizing and TDI Overview

The process of determining the optimal hardware and software resources needed for an SAP HANA system to perform efficiently.

A tool provided by SAP that helps determine the required memory size for an SAP HANA system. It's useful for new SAP implementations and greenfield projects.

A method of deploying SAP HANA by using certified hardware and software components. It provides a pre-configured solution optimized for SAP HANA.

A method of deploying SAP HANA by integrating with existing hardware and software infrastructure. It allows for more customization and flexibility.

The ability of SAP HANA to reduce the amount of storage space required by compressing data in memory.

A special report designed to determine the memory requirements for migrating existing SAP NetWeaver systems to SAP HANA.

A process of determining the optimal hardware resources needed for an SAP HANA system, conducted by SAP experts.

The process of migrating several source systems into one consolidated SAP HANA system.

A list maintained by SAP that certifies specific hardware components compatible with SAP HANA, ensuring performance and reliability.

The minimum network speed required for data transfer between SAP HANA worker nodes, crucial for efficient data processing.

The minimum network speed required for accessing external storage systems, impacting data read/write performance.

A dedicated area within the network used for client connections to the SAP HANA system, including application servers and BI tools.

A guideline provided by storage vendors detailing how to configure their storage systems for optimal performance with SAP HANA.

A service offered by SAP that provides validation and checks to ensure a smooth transition to production for SAP HANA instances.

A process where SAP HANA functionalities are transferred from a legacy system to an SAP HANA system, potentially involving data migration and application adjustments.

The process of transferring a large amount of data from a legacy system to an SAP HANA system, involving data management, transformation, and loading.

The role of an individual who is certified by SAP to install and manage SAP HANA, ensuring adherence to best practices and system stability.

A requirement of SAP HANA tailored data center integration that mandates the use of storage systems listed in an SAP-maintained directory, ensuring their compatibility and support.

A configuration requirement for network setup in SAP HANA tailored data center integration where different network segments handle separate traffic types, enhancing security and efficiency.

A check performed by SAP Active Global Support before a live HANA system goes into production, ensuring smooth operation and identifying potential issues.

The process of determining the necessary RAM capacity for an SAP HANA system, considering both static and dynamic memory needs.

Memory used to store data directly in tables within the SAP HANA database, including the size of uncompressed data.

Memory required for dynamic operations like loading new data or running queries, as it's used temporarily.

A factor used to estimate the amount of RAM needed for SAP HANA to store data efficiently, taking into account data compression techniques.

The amount of disk space needed to store the core data and log files of an SAP HANA system for data protection and recovery.

The process of determining the required processing power or CPU capacity for SAP HANA based on expected query workloads and calculations.

A document that offers detailed information about the features, configurations, and best practices for using SAP HANA.

A document that provides technical details about network requirements and best practices for setting up an efficient network connection for your SAP HANA system.

A tool for determining the necessary size of the disk space for a SAP HANA tailored data center integration setup.

A method for calculating the size of memory for a SAP HANA tailored data center integration setup considering static and dynamic data.

A report in SAP that helps to estimate the memory requirements for an SAP HANA system, specifically for Suite on SAP HANA.

A report in SAP that helps determine the optimal storage space for SAP BW/4HANA systems.

A set of SAP Notes and documents that provide guidance on how to set up a distributed SAP HANA system for scalability and higher performance.

A set of SAP Notes related to virtualizing SAP HANA, providing guidelines for running SAP HANA on virtualized environments like VMware and other hypervisors.

The log volume ensures the recovery of the database with zero data loss in case of faults. SAP HANA records each transaction in the form of a redo log entry.

The minimum size of the log volume depends on the number of data changes occurring between two SAP HANA savepoints, which, by default, are created every five minutes.

The redo log must not be overwritten before a savepoint entry is available in the data volume, otherwise, the SAP HANA database may be unable to restart.

The data volume holds the actual data of the SAP HANA database, while the log volume records changes to ensure data recovery in case of failures.

The recommended size of the data volume is calculated based on the net data size on disk, with an additional 20% for delta merge operations.

During delta merge operations, affected tables are temporarily duplicated on disk for a short period of time. This requires the extra 20% space in the data volume.

For single-node SAP HANA systems, the minimum recommended disk space for /hana/shared/ is shown in the figure, Determine Share Single-Host Size, with a maximum of 1 TB.

The /hana/shared/ file system can be set up as a shared file system, or as a local file system. The advantage of a shared file system is easier conversion to a multi-host system.

All binary, trace, and configuration files are stored under /hana/shared/ for a single-host configuration.

For multi-host (scale-out) systems, all binary, trace, and configuration files are stored on a shared file system that is exposed to all worker nodes of an SAP HANA system in the file system /hana/shared/.

In the installation path (sapmnt), additional space is required per worker node for writing the traces files of a scale-out SAP HANA database system.

Disk space of 1x worker node RAM is recommended for every four worker nodes in a given scale-out system.

For systems with more than 512 GB of in-memory database size, the log volume sizing formula, representing a minimum value.

During the migration of a non-SAP HANA database to SAP HANA, the system may temporarily need more disk space for data than calculated in the sizing phase.

SAP HANA appliances are pre-configured hardware systems certified by SAP for optimal performance with the SAP HANA database. They combine storage, CPU, and other components for a seamless setup.

SAP HANA Hardware Directory is an online resource where you can find a list of certified hardware systems compatible with SAP HANA.

When sizing SAP HANA, you don't need to calculate storage and CPU requirements for SAP HANA appliances. They are pre-configured to meet the demands of the software.

Avoid installing other applications on the SAP HANA database server, except for explicitly supported scenarios.

For non-NetWeaver scenarios, SAP Note 1514966 provides guidance on sizing SAP HANA, but these rules should not be applied to SAP BW/4HANA, Business Suite on SAP HANA, or SAP S/4HANA.

SAP HANA Native Storage Extension is a built-in warm data storage feature that manages less frequently accessed data in SAP HANA without loading it fully into memory.

Data aging in SAP HANA refers to the process of identifying and managing historical data that is no longer actively used, which can improve performance and resource utilization.

Nonactive data in SAP BW/4HANA refers to large amounts of data that are rarely or no longer used, such as historical data.

Nearline storage solutions are used to store cold data, which is data that is very rarely accessed.

SAP HANA Smart Data Access allows you to access remote data through SQL queries as if they were local tables in SAP HANA, without copying the data into SAP HANA.

SAP HANA Dynamic Tiering is an add-on feature that extends SAP HANA memory with a disk-centric columnar store for managing less frequently accessed warm data.

SAP HANA 2.0 requires a minimum of an Intel Haswell CPU or later. This requirement ensures compatibility and optimal performance.

SAP HANA sizing recommendations apply only to certified hardware. You should consult your hardware vendor for compatible configurations.

The SAP HANA development team continuously optimizes the database. It's important to refer to the latest documentation and SAP Notes for accurate sizing information.

The minimum disk space required for a scale-out SAP HANA installation depends on the number of nodes and the storage capacity per node. Each node, except for the Standby node, requires its own disk space.

A Standby node in a scale-out SAP HANA system takes over the data and log volumes of a failed node, so it doesn't require additional disk space.

A complete data backup for SAP HANA includes all data volumes and requires significant storage. Backup size depends on the total data size, the number of backup generations, and the frequency of data changes.

Log backups are essential for point-in-time database recovery and require additional storage based on the number and size of changes in the database.

Storing backups of multiple SAP HANA databases on a single shared storage can impact the overall data throughput during backup or recovery processes, especially when multiple processes run concurrently.

A strategy using only full backups requires significant storage, equal to the total data volume multiplied by the number of backup generations kept on disk.

A strategy combining weekend full backups with workday incremental backups can reduce the overall backup storage requirement.

Exports of database content are sometimes needed for root cause analysis. Storage space should be reserved for these exports, usually around twice the size of the largest database table.

Network bandwidth is crucial for SAP HANA, especially for communication between nodes, administration tools, and clients.

An Admin zone is a network segment often used for managing virtualized environments, administering SAP HANA, and boot server communications.

SAP HANA Appliance deployments typically include internal and storage zones with pre-configured network connectivity. The client and Admin zones are handled separately by customers.

For tailored data center integration of SAP HANA, the internal and storage zones are recommended to have a minimum bandwidth of 10 Gbit/s for optimum performance.

Estimating CPU requirements for migrating to SAP HANA standalone is challenging as there is no direct comparison. A formula of 300 SAPS per active user with a 0.65 utilization buffer can be used as an initial estimate.

Quick Sizer is a tool for sizing SAP HANA database resources based on throughput, number of users and SAP solutions in a hardware-independent format.

Sizing SAP HANA involves an iterative process of gathering information from customers, hardware vendors, and SAP to determine the optimal system configuration.