Show TOC

SAP HANA-Optimized DataStore Object (Obsolete)Locate this document in the navigation structure

Recommendation We recommend that you do not use the DataStore object flagged as SAP HANA-optimized any more. Standard DataStore objects are now automatically optimized for activation in SAP HANA. You can still use existing SAP HANA-optimized DataStore objects, but we recommend reconverting them. To do this, you use report RSDRI_RECONVERT_DATASTORE. You cannot create any new DataStore objects with the flag SAP HANA-Optimized.

The SAP HANA-optimized DataStore object is a standard DataStore object that is optimized for use with the SAP HANA database. By using SAP HANA-optimized DataStore objects, you can achieve significant performance gains when activating requests.

The change log of the SAP HANA-optimized DataStore object is displayed as a table on the BW system. However, this table does not save any data, which helps to save memory space. When the change log is accessed, the data content is calculated using a calculation view. Data is read from the history table for the temporal table of active data in the SAP HANA database.


If you want to view the change log data in the ABAP Dictionary, a warning appears explaining that the table does not exists in the database. This is due to optimization - the table in the database is replaced by a calculation view.

The table for active data is a temporal table that consists of three components: History table, main table and delta table. Data activation is started on the BW system and executed in SAP HANA. No data is transferred to the application server during activation.


In the DataStore object editing screen, you can choose the Unique Data Records property. However, this does not improve system performance when using an SAP HANA-optimized DataStore object. The uniqueness of the data is not checked, meaning that data consistency cannot be guaranteed.

SAP HANA-optimized DataStore objects write a change log entry for every activated record - even if the activation process did not change the active data. This can result in an increased data volume in scenarios where the DataStore object is used to generate a delta (for example, loading master data). In this case, you can specify which activation procedure is used in the maintenance screen for runtime parameters (either system-wide or for individual DataStore objects). You can access the maintenance transaction for runtime parameters in Customizing under Start of the navigation path SAP Customizing Implementation Guide Next navigation step SAP NetWeaver  Next navigation step  Business Warehouse  Next navigation step  Performance Settings  Next navigation step  Maintain Runtime Parameters of DataStore Objects  End of the navigation path. Alternatively, you can access this transaction in the Administration section in the Data Warehousing Workbench, under Start of the navigation path Current Settings Next navigation step DataStore Objects End of the navigation path. Then choose Start of the navigation path SAP HANA Expert Settings Next navigation step Compress Change Log End of the navigation path, to stop unneeded entries being written to the change log.

Differences to a Normal Standard DataStore Object

  • The SAP HANA-optimized DataStore object contains the additional field IMO__INT_KEY in the active data table. This field is required for optimizing SAP HANA and is hidden in queries.

  • A before/after image is still written during activation, even if no changes are made to the active data.

  • It cannot be used as a source of update flows in a 3.x data flow.

    More information: Data Flow in SAP NetWeaver Business Warehouse

  • The complete history of a request is not saved. Only the start status and end status (relating to an activation) are saved.

  • Since real-time data acquisition (RDA) usually involves small data volumes for each activation step, SAP HANA optimization does not produce any advantages. The use of SAP HANA-optimized DataStore objects for RDA is therefore not supported.


You are using a SAP HANA database.