Only 13%-18% of all data in SAP BW is used for reporting. That is our learning of running more than 300 SAP BW analyses. This is vital information that can help SAP BW customers in taking various decisions regarding data management strategy, system performance, and strategies in HANA migrations.
To begin with, we verified what is the typical data distribution in SAP BW systems. The diagram below shows an average SAP BW system based on our analysis and executions of more than 300 BW FitnessTests.
- 13%-18% of BW data (green) is used in reporting (InfoCubes and Master Data)
- 67% of BW data (blue) can be shrunk significantly (DSO, Temporary data, PSA, Change Logs)
There is a significant potential for data management in SAP BW. The main goal is to shrink the system size, but as an added benefit you will speed up the reporting and loading performance. To achieve it, consider these two steps:
1) There is significant part of the SAP BW data that can be cleansed by running regular housekeeping on PSA, Change Logs and Temporary data (Application logs, BI Background Processes, RFC logs IDOCs, etc.). Including Cube compression which might reduce the Cube F data.
2) The biggest chunk of data is DSO and wDSO which can be archived using Near-line Storage into database cluster, Hadoop, RDBMS, SAP IQ, files or others.
The above tips are a must if you are considering migrating your BW to SAP HANA in a cost-effective way. Typically, the business case can be streamlined by implementing automated housekeeping and archiving of data into Near-line Storage.