![Sizing Method for Non-NetWeaver Sizing Method for Non-NetWeaver](/service/media/topic/e67b2989-82fb-49f4-a9d9-1b150d271cf4/HA200_19_en-US_media/HA200_19_en-US_images/Figure 5 The general SAP HANA main memory sizing approach.png)
The SAP Note 1514966 - SAP HANA 1.0: Sizing SAP In-Memory Database describes the sizing of SAP HANA in a non-NetWeaver scenario, for example, when the data is coming from an external data source and SAP HANA is used to model and analyze that data. Do not use these sizing rules for sizing SAP BW/4HANA, Business Suite on SAP HANA systems, or SAP S/4HANA as they will produce incorrect values.
Additional Remarks
For various SAP HANA scenarios, native and third-party technologies provide features to displace data not frequently used either for the SAP HANA persistence or for other database management systems. If such a technology is used, this is considered in the main memory sizing. The following are examples:
SAP HANA Native Storage Extension (SAP Note 2775588) and Data Aging in SAP HANA (SAP Note 2816823)
SAP HANA native storage extension is a general-purpose, built-in warm data store in SAP HANA that lets you manage less-frequently accessed data without fully loading it into memory. SAP HANA native storage extension adds a native warm data tier to an SAP HANA database, managing page-loadable warm data in the SAP HANA database with expanded disk capacity, and an intelligent buffer cache to transfer pages of data between memory and disk.
It integrates disk-based database technology with the SAP HANA in-memory database for an improved cost-to-performance ratio, while complementing other warm data tiering solutions such as SAP HANA extension node and SAP HANA dynamic tiering.
However, it is important to note that SAP HANA native storage extension does not interfere with the existing data aging functionality of SAP HANA. It neither replaces data aging nor changes any aging processes and access in SAP S/4HANA. The SAP S/4HANA data aging tables still remain under the full control of SAP S/4HANA and they must not be changed as any changes to the database tables outside of SAP S/4HANA may result in SAP S/4HANA failure.
- Non-active data concept for SAP BW/4HANA and Nearline Storage Solutions (SAP Note 1767880 and SAP Note 2165650)
Large SAP BW systems contain large amounts of data that are no longer, or rarely, used. However, they remain in the system, for example, historical data, keeping data for legal reasons, and so on. This data is called nonactive data. An implementation for SAP BW/4HANA allows for the displacement of nonactive data if the main memory bottlenecks use a last-recently-used concept. This concept improves main memory resource management, which has positive effects on hardware sizing for a large amount of nonactive data. For more information, see SAP Note 1736976. In addition, nearline storage solutions could be used to store cold data, which can also help to reduce the memory amount.
SAP HANA Smart Data Access 2.0 (SAP Note 2352696)
SAP HANA smart data access lets you access remote data via SQL queries as if they are local tables in SAP HANA. You don't need to copy the data into SAP HANA first. This capability provides operational and cost benefits and supports the development and deployment of the next generation of analytical applications, which require the ability to access, synthesize, and integrate data from multiple systems in real-time, regardless of where the data is located, or what systems are generating it.
Deprecated: SAP HANA 2.0 Dynamic Tiering (SAP Note 3414255)
SAP HANA dynamic tiering is an optional add-on to the SAP HANA database for managing historical data. Its purpose is to extend SAP HANA memory with a disk-centric columnar store (as opposed to SAP HANA’s in-memory store) for managing less frequently accessed warm data. Warm data has relaxed performance requirements compared to highly active "hot" data. Data in the extended store is on line, and available for both queries and updates. Although it is possible to add dynamic tiering to small SAP HANA databases, dynamic tiering is targeted at SAP HANA database sizes of 512 GB and larger, where large data volumes begin to necessitate a data lifecycle management solution.