You can use a program to define how DataSources and write-optimized DataStore objects should be treated with regard to multi-temperature data management with SAP HANA dynamic tiering.
You can select and change the multi-temperature category of DataSources, write-optimized DataStore objects and semantically partitioned objects that are only made up of write-optimized DataStore objects. You can define whether SAP HANA tables or extended tables should be created for objects (corresponds to the setting in the object maintenance) and whether data contained in the objects should be moved.
Note that DataSource objects (advanced) are not covered by this program.
|Warm (Extended Storage)||For the selected objects, SAP HANA dynamic tiering should be used with extended tables.|
|Hot (In-Memory)||For the selected objects, the data should be located in the main memory of the SAP HANA database.|
|Change Metadata||In the metadata of the selected objects, you can define whether a SAP HANA table or an extended table should be generated when an object is activated and the corresponding prerequisites are met. This action corresponds to the setting that you can make in the maintenance transaction for the write-optimized DataStore object or in the DataSource. Note that this action represents a metadata change, and that selecting this field does not cause existing data to be moved.|
|Move Data||You can define whether existing data in the selected objects should be moved. This means that the data is moved either from the SAP HANA Table to the extended table or in the other direction, depending on which multi-temperature category is selected.|
|Restart Canceled Data Moves||This option is only relevant if the data move has been canceled. In this case, you can define that the data move for the selected objects should be restarted automatically. The system then moves the data that has not been moved yet.|
The list of objects displayed here depends on which actions you have selected. If you have selected Warm (Extended Storage) as the category and Move Data as the option for example, the system will display all objects whose data is stored in SAP HANA tables and that should be moved to extended tables.
If the current status of an object does not match the settings made in the program, the system performs the action in question when executing the program.
While the system moves the data, the tables of the objects are locked and cannot be accessed. This also applies if the move is canceled. The lock applies until the data move is completed after the program is executed again with Restart Canceled Data Moves.
A semantically-partitioned object is made up of multiple write-optimized DataStore objects that have the same structure. It therefore has multiple tables. There can also be multiple tables for a DataSource if it is segmented or if there are multiple PSA versions for it. If some of these tables are in extended storage and others are not, the program tries to move the data in accordance with the setting for the object's metadata (Change Metadata) when performing the Move Data option.
You can call the execution log in transaction SE38. To do this, execute program RS_DYNTIER_CHANGE, press Display Previous Logs and set the criteria for the log that you are looking for on the screen that opens.