The Ultimate Guide to Effective Sizing of SAP HANAIt is vital to size your SAP HANA hardware correctly to realize the maximum benefit from your investment and reduce your long term total cost of ownership. Inadequate and over provisioned sizing of SAP HANA could lead excess capacity and bloated hardware while under provisioning can cause unexpected delays which will increase the cost of operational performance. For the most part, sizing of SAP HANA database is based on the main memory which is determined by the amount of the actual data stored in memory. Since the data is compressed in HANA and the compression results depends on the used scenario, it is not easy to guess the amount of memory needed for sure. Sizing-in-the-SAP-Service-Marketplace-Crop.png' alt='Sap Sizing Tool For Hardware Sizing Tools' title='Sap Sizing Tool For Hardware Sizing Tools' />References and further reading SAP Quick Sizer tool. SAP Standard Applications Benchmark. SAP Note 1514966 SAP HANA 1. Sizing SAP InMemory Database. Neo Sans Std Light here. SAP AG Business Intelligence 4 Sizing Guide PreSizing Checklist These are the things you need to do before you start your sizing exercise. This blog provides information about running SAP Applications on the Microsoft Platform. The blog is written by people who are working with SAP on the. Typically, banking services from SAP 9. FSAPPL 500 can be installed using the one instance or the twoinstance approach For details, please see the Component. Sap Sizing Tool For Hardware Sizing Tools' title='Sap Sizing Tool For Hardware Sizing Tools' />Therefore, the memory sizing for SAP HANA should be performed using SAP Quick Sizer tool, relevant SAP notes and SAP sizing reports. Depending on the SAP HANA deployment, sizing approach would be different. SAP Quick Sizer. For SAP HANA greenfield implementations, it is necessary to size the memory using the SAP Quick Sizer tool. The Quick Sizer calculates CPU, disk, memory and IO resources based on the throughput numbers and can help you translate business requirements into technical requirements. For greenfield sizing, complete the following steps Access the Quick Sizer tool SAP HANA versionCreate a sizing project input your customer scenario data into Quick Sizer and it will display the results. Check for sample configurations and find the appropriate hardware configurations on SAP Standard Application Benchmark http www. Provide the project name to your hardware vendor and they will be able to propose an appropriate hardware configuration. If you are unable to find the right sizing for your SAP product in the Quick Sizer tool, consult the sizing guidelines and SAP notes details belowSimply fill the online questionnaire based on business oriented figures and the results you obtain can help you select an economically balanced system that matches your companys business goals. This is especially useful for initial budget planning. SKU171577/6b66a161-2b03-9ef2-e393-3a516d23882e.jpg' alt='Sap Sizing Tool For Hardware Sizing Tools For Copper' title='Sap Sizing Tool For Hardware Sizing Tools For Copper' />Sizing BW on HANAFor systems that are migrated to SAP HANA, if the migration is from an SAP Net. Weaver based system, use the sizing reports provided by SAP For BW on HANA migrations, use the following SAP notes These two SAP notes explain the sizing approach of SAP BW system on SAP HANA including the sizing report and guidelines. The sizing here includes the memory sizing column, row store and additional components and disk sizing for data and log files. Note that the report could run up to 8 1. Production system first. Below figure shows an example sizing report result for SAP BW on SAP HANA memory Sizing Suite on HANA, S4. HANAFor Suite on HANA migrations, use the following SAP notes These two SAP notes describe the approach for Business Suite system on SAP HANA and SAP S4 HANA. There is also a sizing script and guideline attached to these notes. See below for an example sizing report for Suite on SAP HANA memory After getting the memory sizing results via sizing reports described in the above SAP notes, check SAP HANA Hardware directory for hardware that matches your memory sizing results. For now, you dont need to worry about storage and CPU sizing as they are already included in the certified SAP HANA appliances. Sizing SAP HANA for non Net. Weaver approach. If the migration is from a non SAP Net. Weaver data source, you can use the approach described in SAP Note 1. SAP HANA 1. 0 Sizing SAP In Memory Database. Adding Hulu To Hisense. This SAP note explains the sizing of SAP HANA in a non Net. Weaver scenario, for instance, if the data is coming from an external source for SAP HANA to process and analyse. These sizing rules should not be used for sizing SAP BW or SAP Suite on HANA or SAP S4. HANA sizing. General sizing approach for SAP HANA for the non Net. Weaver approach is basically determining static and dynamic memory requirements. The static memory requirement is related to the amount of main memory that is used for holding the table data which is the amount of disk space covered by the corresponding database tables indexes not included. It is required to calculate the uncompressed data volume that is to be loaded into HANA using the tools attached to SAP Note 1. Additional memory is required also for objects that are created dynamically when new data is created or queries executed. Simply multiply static memory requirement by two as it is recommended by SAP to size dynamic memory same as static memory. Sizing SAP HANA for Tailored Data Center Integration TDIIf you are planning to build SAP HANA system based on SAP HANA TDI Tailored Data Center Integration approach by using the available hardware or to reuse existing hardware to reduce hardware cost, you must become TDI certified and meet SAP HANA storage requirements. TDI follows the approach of SAP sizing and mapping to authorized servers, network and storage. Sizing SAP HANA TDI consists of three main steps Memory sizing for static and dynamic data. Disk sizing for persistence storage. Best Podcast App Windows Phone 7. HTB1tQjLPXXXXXX.aXXXq6xXFXXXf/1-2-6mm-Woodworking-Milling-Cutter-Tungsten-steel-Carpentry-Engraving-Tools-TCT-Round-bottom-knife-5133.jpg' alt='Sap Sizing Tool For Hardware Sizing Tools' title='Sap Sizing Tool For Hardware Sizing Tools' />
CPU sizing for transactions, queries and calculations. As the first step to sizing SAP HANA TDI system, you should perform a memory sizing. Depending on the use case, you can use SAP Quick Sizer andor above SAP notes for sizing SuiteBW on HANA. IBM also provides a process to support mapping of the SAP sizing to a hardware configuration that would meet your sizing demands. For more information, see SAP Note 2. See below for more details about Disk and CPU sizing. Disk Sizing. Persistent storage distinguishes between the data volume and log volume. In the data volume, basically a copy of the in memory data persists and changed data is written to the data volume. The log volume is required to ensure the recovery of the database with zero data loss in case of a failure, so each transaction in SAP HANA is recorded as a redo log entry. The recommended size of a data volume is equal to the calculated results from the sizing reports. Use value Net data size on disk and an additional free space of 2. The figure shows an example sizing report result As you can see the sizing report, net data size on disk is calculated around 1. TB. In this case, our minimum requirement for data volume would be around 1. TB, considering the additional 2. During the migration of non HANA DB to SAP HANA, the system may require a little more space than the actual calculated net data size on disk, but with enterprise storage, that is not considered relevant for the overall storage sizing. The minimum size of log volume depends on the number of data changes occurring between two SAP HANA savepoints which is by default created every five minutes. More data changes happening during this time means more redo logs are generated in the log area. When sizing the log volume, you need to consider following points The redo logs must not be overwritten before a savepoint entry is available in data volume. This might cause SAP HANA system unable to restart. During the migration process, a very high workload needs to be processed, so it would be better to allocate extra disk space for the log volume in case of regular redo log backups fail for some reason during the migration. The result of memory sizing usually determines sizing of the log area. If the total memory requirement is less than 5. GB, log area should be at least half of the total memory requirement. If your system requires more than 5. GB memory, you should at least allocate 5.