Save database space in your SAP® BW (housekeeping)
Delete data from InfoProviders that not being used
With the help of 4C™ SAP® BW alert pack you can identify InfoProviders, dedicated for reporting, but without reports running against them or with reports that run long time ago. In a picture below, there is an alert output, showing the list of InfoProviders, uploaded on a daily basis. Two of them however, were used in reporting for the last time years ago. These two InfoProviders are potential candidates for data deletion. Working with dozens of BW clients, we identify such cases, allowing to save substantial amounts of BW database space.
Control the size of PSA tables
With the help of 4C™ SAP® BW alert pack you can monitor the number of records, uploaded into BW PSA tables. PSA tables, when neglected, can grab unnecessarily large amounts of storage holding useless data. These tables should be trimmed as part of your regular housekeeping, which is trivial, while using 4C™ SAP® BW alert pack. Determine a threshold (e.g. number of records in the PSA table > 100’000) which when reached, will generate and send an appropriate notification. In a picture below, there is an alert output, showing the list of the PSA tables, with the number of records, residing in each table. 4C™ SAP® BW alert pack helps to control the number of PSA records and requests, allowing to save substantial amounts of BW database space.
Control the size of DSO Changelog tables
Are you running delta dataloads from one or more DSOs into other InfoProviders? If so, then you are using the DSOs changelog tables each time you load a further request. DSO changelog table keeps track of the changes in the data that come about each time a delta request is loaded into a DSO. Once the data has been activated in the DSO, it is unlikely that you will need the changelog data again, so you should trim your DSO changelog tables or they will become very large. It’s normal to trim data older than 10-30 days from each DSO changelog as part of your regular housekeeping tasks. With the help of 4C™ SAP® BW alert pack you can easily identify and alert on the DSO changelogs, that have become too large . In a picture below there is an alert output, showing the list of the changelog tables. The very large ones (millions of records) are potential candidates for data deletion. Working with dozens of BW clients, we identify such cases, allowing to save substantial amounts of BW database space.
Identify rarely used BW Aggregates
With the help of 4C™ SAP® BW alert pack you can identify InfoCubes, backed up by Aggregates. Aggregates allow quick access to InfoCube data during reporting. Similar to database indexes, they serve to improve performance. However, there are numerous cases in which reports that previously accessed Aggregates have stopped using them. It can happen if, for example, the report was changed or if the structure of Aggregate itself was altered, resulting in deteriorated query performance. 4C™ SAP® BW alert pack identifies and alerts on such cases. In example below, there is an alert, presenting the list of the InfoCubes with the last Aggregation call. You can clearly see from report, which Aggregates are not being accessed or were used long time ago. Such Aggregates are potential candidates for further investigation. Working with dozens of BW clients, while using 4C™ SAP® BW alerts we identify such cases, allowing to improve query performance and save substantial amounts of BW database space.
