on 12-03-2015 7:38 PM
Hi!
We are evaluating Data Aging implementation to optimize our SoH memory usage, but some of the SAP tables we are planning to include in this process don't have Data Aging Object.
If we create our own Data Aging objects that might include SAP standard tables, what will happen if SAP delivers new objects?
Did anyone out there implemented such process?
Cheers,
Fernando Figueiredo
Hi Fernando,
My understanding of data ageing is that for SAP-delivered tables, you should really only use the SAP-delivered data ageing objects. The ability to create your own data ageing objects is so that you can include your own (Z) tables in your data ageing strategy. Although it is possible to create data ageing objects for SAP-delivered tables, I have a feeling that it might not be such a good idea - at the very least, you may run into problems as you said when SAP does deliver objects for those tables.
To optimise your SoH memory usage, you might be better off looking at HANA Dynamic Tiering and NLS using the Data Lifecycle Manager.
Cheers,
Kevin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.