Sizing SAP NetWeaver Business Warehouse 3.5 Systems for (BW on HANA)
You have an (SAP NetWeaver Business Warehouse 3.5) system and you have decided now that you want to migrate from the traditional database platform to SAP HANA and you are looking for information on the hardware sizing for the SAP HANA.
You would like to understand the following before migrating your SAP NetWeaver Business Warehouse (BW) systems to SAP HANA:
- The current memory footprint of the system including all tables, Indexes, etc
- How data is distributing in BW objects i.e. DSO’s, PSA’s, Infocubes, etc
- How much of memory would be required to migrate successfully to the SAP HANA database?
- How many nodes would be recommended to migrate to SAP HANA with their estimated size?
- Disk space requirement – Data
- Disk space requirement – Logs
You can find the information about these questions in SAP note 2021372.
Since the Netweaver BW, 3.5 is quite old and out of maintenance the SAP HANA sizing report that is used for newer versions of SAP Netweaver BW would not work on the (3.5 environments) hence you should use the attached sizing report in SAP note 2021372-Sizing Report for BW on HANA (for SAP NetWeaver Business Warehouse 3.5 Systems)
In the attachment sections of this SAP note, you will see (ZBW_HANA_SIZING_FORBW_35.zip).
Within the attachment, you will see the below 3 files. Make sure you read the (README.TXT) file before you proceed with any task.
There is a little bit of manual effort required for this however SAP has provided in the attachment the 2 ABAP files that are to be created within the target system so you will not have to create the programs and function modules from scratch.
Please review the README document that is provided within the SAP note 2021372 Zip Folder before you proceed doing anything.
If you have any questions about what is explained above please feel free to ask them below in the comment section. If you have any questions regarding SAP BW on HANA or SAP BW/4HANA Sizings in general, please post them into our Q&A section in the link below: