Skip to Content

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 cold.

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.

Overview:


Data Tiering Optimization helps SAP BW/4HANA customers to classify the data in the DataStore object (advanced) as hot, warm or cold, depending on the cost and performance requirements for the data.

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. Only SAP HANA Extension Nodes can be used for warm data storage in SAP BW/4HANA – SAP HANA Dynamic Tiering is not applicable to SAP BW/4HANA.
  • External Tier (cold): The data is stored externally (SAP IQ, Hadoop or SAP Vora (the latter two are only available with SAP BW/4HANA 1.0 FP08 or higher)).

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

Videos:


  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.

Getting started

General Information


Set Up and Installation


Cold Store with SAP IQ (fka Nearline Store)

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

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Mihir L Kiri

    Hi Gordon,

    What does “Dynamic Partitioning Schema” mean ? It is mentioned in “Future direction”. Doesn’t it contradict when we say “SAP HANA Dynamic Tiering is not applicable to SAP BW/4HANA.”

    Or the is a mistake in my understanding.

    Regards,

    Mihir Kiri

     

     

    (0) 
    1. Gordon Witzel Post author

      Hi Mihir,

      “Dynamic Partitioning Schema” means  that the partition is able to cope with additional data outside of the expected range and DTO is able to self extending partitioning schemes.

      Furthermore for warm data in DTO we are using Extension Nodes (additional Hana Scale Out node with a relaxed sizing formula and RAM/CPU ratio. Therefore SAP HANA Dynamic Tiering is not applicable and not supported with SAP Data Tiering Optimization.

      BR Gordon.

       

      (1) 

Leave a Reply