Skip to Content
Executive Summary
  
SAP HANA is nothing but the combination of software and Hardware innovation. When we talk about the hardware innovation, the term comes as In-memory computing where the major role is played by the random access memory (RAM) used in the server.
  
SAP HANA (High Performance Analytic Appliance) is a game-changer in the database innovation. HANA is designed to provide real-time analytics and transactional processing at lightening speeds, which is possible because of the in-memory technique where all the processing is done in the memory and actually disk is only used for the persistency.
The critical factor for SAP HANA implementation is the right sizing of the server based on the business requirement and when we talk about
right sizing, it means amount of memory, the CPU processing power which needs to be calculated.
For the purpose of successful SAP HANA implementation, SAP has provided various guidelines and methods to calculate the correct hardware size. Here we will study these methods for the successful SAP HANA implementation.
Introduction
In the below paper we will study about the SAP-HANA sizing for the optimal performance of the SAP HANA implementation project with different scenarios.
Sizing is one of the critical factors for SAP HANA and hence SAP has provided various methods to achieve the accurate size based on the client
requirements. One can use any or all of the methods to calculate the size for their SAP HANA instance.
Basically we will divide the sizing calculation based on two scenarios,
1. SAP HANA sizing for standalone instance (Side-by-side scenario)
2. SAP HANA sizing for BW on HANA
  
Recently SAP has announced CRM on SAP HANA and SAP Business Suite on SAP HANA. The sizing calculation for these scenarios is not covered in this paper. As these scenarios are rolled out for ramp-up customers and general availability will be in the 2nd or 3rd quarter of 2013.
Below is the list of methods one can utilize to calculate SAP HANA sizing. Only the first method will be used for the standalone instance and for SAP BW on HANA, we can use any of the below method:
1. SAP HANA sizing using the QuickSizer tool
2. SAP HANA sizing using the DB specific scripts
3. SAP HANA sizing using the ABAP report
     
Problem Definition
 
How to calculate server size for the SAP HANA implementation to achieve the optimal performance benefit and ROI on SAP HANA?
  
Solution Details
  
As mentioned above depending on the project status, the sizing exercise can be performed. There are basically three methods to calculate the size; we will study these methods in detail below.
 
SAP HANA sizing calculation using QuickSizer:
 
The QuickSizer method is useful for the customers who will be implementing SAP HANA instance as a standalone instance or performing the
implementation from scratch with limited details about the data models for SAP BW scenario.
In QuickSizer there are three scenarios,
 
  1. Standalone HANA
  2. SAP NetWeaver BW powered by SAP HANA
  3. HANA Rapid Deployment Solutions
Description Screen Shots
Start the QuickSizer tool: https://websmp109.sap-ag.de/quicksizer
Create New Project
/wp-content/uploads/2013/01/1_175263.jpg
Choose Standalone HANA
 
HANA memory sizing is derived from the size of the tables in the source database. Note that only tables must be taken into account. Space for indexes, temporary table spaces etc. must be excluded. Run the sizing script attached to SAP note 1514966 to obtain correct size information from your source database system catalog.
 
The number of users is optional. If you enter a user number, Quick Sizer checks if the CPU requirements are met by certified hardware configurations.
/wp-content/uploads/2013/01/2_175264.jpg
Specifics for Standalone HANA
 
  • Enter the number of concurrent users
  • Enter the source data footprint in GB
Enter the compression factor, i.e. the ratio of the sizes of uncompressed data tables (without their indexes) on the source database and the memory requirements of these tables in HANA. We strongly recommend using the default value if you do not have reliable information justifying a different compression factor.
Input:
/wp-content/uploads/2013/01/3_175278.jpg
Output:
/wp-content/uploads/2013/01/4_175279.jpg
Specifics for SAP NetWeaver Powered by SAP HANA
 
  • Enter the Avg workday & Peak Load time
  • Enter the user groups based on the usage, basically there are
    three types of users: Information Consumer, Business Users, Expert Users
  • Enter the Data Upload records
  • Enter the Row Table Footprint, Column Tables Footprint and Column
    Compression
  • Enter InfoCubes details
  • Enter DataStore Objects
/wp-content/uploads/2013/01/5_175280.jpg
Input:
/wp-content/uploads/2013/01/6_175281.jpg
Output:
/wp-content/uploads/2013/01/7_175282.jpg
Once you calculate the required results, send email to your preferred hardware partner with the QuickSizer project name and HW partner will
prepare the SAP HANA appliance system as per the calculated results.
 
SAP HANA sizing using the DB specific scripts
Unix/Linux and Windows scripts draw information from database dictionary tables to determine size of tables in database (excluding indexes,
temp table spaces, etc.)
DB specific scripts and sizing information provided by note 1637145 – In this note, Database platform specific scripts have been attached
which analyze the database catalog and determine the overall database table’s footprint for both row store and column store.
The note contains an attachment “get_size.zip” which has all the DB specific shell scripts. Below, I have used the script for MS SQL server to
calculate the HANA DB size. Please make sure that you extract the platform specific script along with the file “load_RowStore_List.sql” before
you execute the script.

Description Screen Shots
Download “get_size.zip” from SAP Note 1637145 /wp-content/uploads/2013/01/8_175283.jpg
Extract and copy the DB specific scripts under below path,
/usr/sap/<SID>/sys/global
Note: Same folder where the rowstorelist.txt file is stored
/wp-content/uploads/2013/01/9_175284.jpg
Edit the “get_mss_size.sql” script file to add,
In line 1 of the script, replace “SID” with the SID of your system
 
At the bottom of the script, replace “schema” in the command exec sp_hana_sizing ‘schema’ by the schema name of your system
/wp-content/uploads/2013/01/10_175285.jpg
Run the get_mss_size.sql script,
SID: S01
 
Schema Name: S01
/wp-content/uploads/2013/01/11_175286.jpg
Output:
/wp-content/uploads/2013/01/12_175287.jpg

Sizing Calculation:

 

SAP has provided the sizing formula based on the output from the sql script. Use the output from sql script to calculate the RAM size and Disk
Size.

RAM = (colstore tables footprint * 2/4 + rowstore tables footprint /1.5) * C1) + 50 GB (HANA Cache and Additional Services)

e.g: RAM: (4.09 *2/4 + 8.33/1.5)*5) + 50 GB = 88 GB

 

Disk = (Disk – Persistence (4*RAM) + Disk – Log (1*RAM))

e.g: (4*88 + 1*88 = 440 GB)

SAP HANA Sizing Using ABAP Report:

Starting with the BW version 7.3 SP5 you can run the SAP BW on SAP HANA DB platform, In order to migrate an existing SAP BW system from any DB platform to SAP HANA, SAP recommends using the new ABAP sizing report /SDF/HANA_BW_SIZING for SAP BW.

 

  • The ABAP report provides much better accuracy of sizing results.
  • Handles source DB compression ration
  • Uses table type specific compression factors
  • Produces detailed results as compared to DB scripts or quick sizer tool method
  • ABAP report is independent of source database
  • Option to select the future growth calculation of memory and disk size

           

The pre-requisite for ABAP report /SDF/HANA_BW_SIZING is support tool plug-in version ST-PI 2008_1_7XX SP06

This report obtains list of tables from the ABAP dictionary table (DD02L)

 

For more details, please refer SAP BW on HANA Sizing Report: https://websmp209.sap-ag.de/~sapidb/012006153200000051552013E/SAP_BW_on_HANA_Sizing_Report_V1_4.pdf

Description Screen Shots
Login to SAP BW System and run t-code SE38 > Enter the report name “/SDF/HANA_BW_SIZING” and execute /wp-content/uploads/2013/01/13_175288.jpg
This is the sample input & output screen for
the ABAP report

Input:

/wp-content/uploads/2013/01/14_175289.jpg

Output:

/wp-content/uploads/2013/01/15_175290.jpg

Input:

 

I am using below input fields specific to the case below, one can change the inputs as per the business requirements

 

Enter the inputs as below,

 

Store output in file = X

File Name = Extent.ext (Default File Name)

Number of parallel procs = 50

Suppress Table with Zero size = X

Precision = Low (Low precision with take minimum time to execute
the report)

Future Growth = X

Number of Years = 3

Relative Growth in % and Growth value = 100 GB

 

Output:

RAM: 60 GB

Disk: 300 GB (5 times RAM)

Input:

/wp-content/uploads/2013/01/16_175291.jpg

Output:

/wp-content/uploads/2013/01/17_175292.jpg

Business benefits

The important benefit for the right amount of SAP HANA sizing is to achieve the unparallel speed to access and output real-time data. SAP HANA’s in memory storage capacity allows the processing of massive quantities of real-time data to provide the immediate results to end users because of the huge amount of memory.

The right sizing at the start of the project will help in getting the ROI on SAP HANA and help in reducing the future maintenance cost because of the data volume growth over the period of time.

 

The SAP HANA sizing will help in identifying the requirement of single node system or scale out system requirements based on the existing
system data volume and future growth analysis

Conclusion

The need for SAP HANA sizing is very important in the initial phase of SAP HANA implementation. Improper sizing or missing sizing exercise will lead to various issues in terms of performance and the whole purpose of HANA implementation will be lost.

References

SAP Note 1736976 – Sizing Report for BW on HANA

https://websmp209.sap-ag.de/~sapidb/012006153200000051552013E/SAP_BW_on_HANA_Sizing_Report_V1_4.pdf

SAP Note 1514966 – SAP HANA 1.0: Sizing SAP In-Memory Database

How To Size SAP BW on HANA

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

  1. Mike Hibbert

    I can’t see a SYBASE specific query and the SQL Server version refers to sys.tables and dbcc showfilestats – neither of which occur in SYBASE.

    Is there a SYBASE version or have you any details about the changes I’d need to make?

    (0) 
      1. Fenton Morris Winmill

        But everything entered into the Standard Quicksizer will have to be re-entered manually.

        Having the ability to compare sizing results between Classic and HANA would be of great advantage

        (0) 

Leave a Reply