|
Created by: |
SAP |
|
Underlying SAP report: |
RSTBPDEL |
|
Client-dependent: |
No |
|
Settings as variant: |
Yes |
|
Support for RecycleBin: |
No |
|
Recommended for HANA pre-migration Housekeeping: |
Yes |
Once the table logging is activated, you can review the history of changes made in custom tables. These changes are saved in the table DBTABLOG. Logging is carried out record by record, which means that for every change operation, the image of the previous state is written to the log table. This approach consumes a lot of space, so it is really important to adopt a well-balanced table logging policy to ensure that the data growth of the table DBTABLOG is acceptable.
It is possible to delete the data saved in DBTABLOG using the report RSTBPDEL.
Our recommendation is to prepare a table logging policy and to decide together with the data owners which tables will be logged.
Activating logging in a table has an important disadvantage – updates/modifications to the Z tables for which logging is activated can become slow.
