Reduce TCO for SAP and SAP HANA native applications; increase capacity and data volume management
Prepare IT for Optimizing SAP with Native Application Data Management & Placement
Dell EMC Broad Solutions Portfolio
Run SAP from edge to core to hybrid cloud.
As organizations scale the adoption of the SAP HANA database for next generation “data driven” intelligent enterprise applications, IT must have a strategy for managing TCO and SAP HANA licensing costs. By reducing the amount of data that must be maintained in expensive DRAM, IT can safeguard maximum data value at the minimum cost.
With the introduction of SAP HANA data tiering, SAP gives IT a framework for managing data placement based on the data value and SLA over time.
SAP Data Tiering Options
Hot Store is used to store mission-critical data for real-time processing and real-time analytics. Persistent memory (PMEM) extends the in-memory storage capacity for hot data in SAP HANA.
Warm Store is for less critical data with reduced performance and SLAs that can be stored on lower cost storage but still managed as part of the SAP HANA database.
Cold Store: SAP HANA cold data tiering provides persistence capabilities for HANA cold data in external data stores, like HDFS, Azure Data Lake and SAP Big Data Services.
Which Data Tier Should You Use?
The answer; it depends. A data tiering strategy needs to be aligned with your SAP HANA deployment – the data processing tier, cost and performance characteristics must be suited to the application profile.
This SAP blog provides a good introduction to recommended data tiering approaches for SAP and native applications.