Get Even More Visitors To Your Blog, Upgrade To A Business Listing >>

SAP BW/4HANA Data Tiering Optimization

Dear friends of SAP BW/4HANA,

I’m working for SAP since more than 10 years and as a member of the BW product management team I received a lot of questions from customers regarding new functionalities for data lifecycle management and data aging strategies in SAP BW/4HANA.

Therefore, I would like to share a summary of the currently available information.

With SAP BW/4HANA 1.0 SP04 SAP is providing functionality to classify persistent BW data into hot, warm and hold.

In this blog, I’ll explain the advantages of the SAP BW/4HANA exclusively available new feature for Data Tiering Optimization (DTO) in technical details.


Data Tiering Optimization helps SAP BW/4HANA customers to classify the data in the DataStore object (advanced) as hot, warm or cold, depending on how frequently it is accessed.

Depending on this classification and how the data is used, the data is stored in different storage areas. Data Tiering Optimization provides a central UI, where all storage options can be set. The partitions from the SAP HANA database are used for this.

The following options are available:

  • Standard Tier (hot): The data is stored in SAP HANA.
  • Extension Tier (warm): The data is stored in a SAP HANA extension node.
  • External Tier (cold): The data is stored externally (SAP IQ, Hadoop or SAP Vora). Please note that Hadoop-based external storage is currently only possible via SAP NLS data archiving processes and not via DTO.

Overview presentation:

SAP Data Tiering Optimization is an option to optimize the memory footprint of data in SAP BW/4HANA and streamline administration and development, thereby reducing TCO.

Introducing one data tiering concept for hot, warm and cold data based on Advanced DataStore Objects enables users to create full flexible partitions based on the data temperature in SAP BW/4HANA. Find the full presentation here:

Data  Tiering  Optimization with SAP BW/4HANA


  1. Build a aDSO and creating partitions for hot, warm and cold data.
  2. Creating a query based on the aDSO partitions.
  3. Reload a partition and assign the data to a new temperature level.
  4. Merge and enhance the partition and distribute the data across the different partitions.
  5. Create a Semantic Group, define the members and assign the partitions to different temperature levels.

Getting started

Set Up and Installation

Cold Store with SAP IQ (fka Nearline Store)

  • SAP First Guidance – SAP BW: Implementation SAP-NLS/SDA with SAP IQ16.0
  • Please note that the respective Remote Source (HANA SDA) to IQ (ODBC) needs to be “readwrite” enabled
  • Configuring SAP IQ as a Near-Line Storage Solution
  • SAP Note 1796393 – SAP BW near-line solution with SAP IQ
  • SAP IQ 16 Hardware Sizing Guide
  • End-to-end Document — SAP IQ as a Near-line Storage Solution for SAP BW

Warm Store with Sap Hana Extension Node

  • SAP Note 2343647 How-To: Configuring SAP HANA for the BW Extension Node
  • SAP Note 2453736 How-To: Configuring SAP HANA for SAP BW Extension Node in SAP HANA 2.0

General Information

  • SAP Note 2296290 – New Sizing Report for BW/4HANA

Implementation and Administration

Cold Store with SAP IQ (fka Nearline Store)

  • SAP Note 2165650 FAQ: BW Near-Line Storage with HANA Smart Data Access
  • SAP Note 2100962 FAQ: BW Near-Line Storage with HANA Smart Data Access: Query Performance
  • SAP Note 1999431 SIQ: Setting up SSL for connections to IQ
  • SAP Note 2133194 Can SAP IQ run in a cloud environment?

Warm Store with SAP HANA Extension Node

  • FAQ: SAP BW/4HANA and SAP BW-on-HANA with SAP HANA Extension Nodes
  • SAP Help Portal: Using an Extension Node for Warm Data
  • SAP Note 2334091 BW/4HANA: Table Placement and Landscape Redistribution
  • SAP Note 2317200 Data lifecycle management for BW on SAP HANA and extension nodes

General Information 

  • SAP Help Portal: Data Tiering Optimization in SAP BW/4HANA
  • SAP Note 2517460 – SAP BW/4HANA Data Tiering Optimization: Information, Recommendations and Limitations

This post first appeared on Web Service Testing A Blackjack GUI And API, please read the originial post: here

Share the post

SAP BW/4HANA Data Tiering Optimization


Subscribe to Web Service Testing A Blackjack Gui And Api

Get updates delivered right to your inbox!

Thank you for your subscription