Principles of SAP HANA Sizing - on premise and cloud-1.pdf

PUBLIC
Sebastian Schmitt, SAP
2022
Principles of SAP HANA Sizing —
on premise and cloud

2
PUBLIC
© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other
agreement with SAP. SAP has no obligation to pursue any course of business outlined in this
presentation or to develop or release any functionality mentioned in this presentation. This
presentation and SAP's strategy and possible future developments are subject to change and may
be changed by SAP at any time for any reason without notice. This document is provided without a
warranty of any kind, either express or implied, including but not limited to, the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility
for errors or omissions in this document, except if such damages were caused by SAP intentionally
or grossly negligent.

3
PUBLIC
Sizing Introduction and Basics
Sizing Tools and Results
Sizing SAP HANA
Wrap-up
Agenda

4
PUBLIC
Sizing KPIs
▪ Different sizing approach: SAP
HANA sizing vs. sizing of traditional
DB
▪ Memory is the leading driver for
SAP HANA sizing
▪ Massive parallelization in analytical
scenarios will have an influence on
Response Times; hence CPU
requirement will get more important
for analytical scenarios
▪ Mixed transactional and analytic
workloads now possible with SAP
HANA but compete for shared
resources
▪ Disk is required for data persistence and for logging data
▪ Sufficient I/O performance required to enable processes to run
with acceptable data throughput and storage system latency.
Disk size
Disk I/O
▪ Compared to anyDB, more CPU power is required to fully
benefit from the parallel processing capabilities of SAP
HANA for optimal response times
CPU
▪ Memory sizing depends on the data footprint in SAP HANA
(business and meta data in column and row store)
▪ Memory is also used by other components (e.g. SAP
HANA caches) and for processing of requests
Memory
▪ Network sizing typically focuses on the bandwidth and is
described in gigabits per second (gbps)
Front-end
Network Load

5
PUBLIC
Memory: Leading Driver for SAP HANA Sizing
▪ The main driver for memory sizing is the table data of the planned SAP HANA system
▪ Most tables are located in the highly compressed column store of SAP HANA
▪ For working memory of the database and temporary calculations, almost the same size as for table data is
required additionally
▪ An SAP HANA database includes further memory areas, such as code, stack, caches, operating system, and
other system files. These areas are typically small compared to a typical database.

6
PUBLIC
Different Types of Sizing
Greenfield Sizing
Sizing of new applications from scratch
Brownfield Sizing
Extension / migration of an SAP system
Bluefield Sizing
Re-implementation of an
existing system
Hardware Budget Sizing
Smaller companies
▪ Tools: Sizing Guidelines, Quick Sizer (user)
▪ Very simple algorithms
▪ Assumptions, likelihoods
Medium to large companies
▪ Tools: Sizing Guidelines, Quick Sizer (throughput)
▪ Usage of standard tools
▪ Focus on core business processes
Re-Sizing
▪ Tools: SAP system monitors
▪ Goal: Extend an existing system by load
− e.g.,100 additional users who'll do the same as the current productive
Selective Data Transition*
▪ Tools: S/4HANA & BW/4HANA
Sizing Reports
▪ Re-Implementation with
Selective Transactional Data
* Special case
Shell copy: Re-implementation
without transactional data, but with
old customizing and master data
Upgrade Sizing
▪ Tools: SAP system monitors
▪ SAP Notes
▪ Goal: Upgrade SAP software
Migration Sizing
▪ Tools: S/4HANA and BW/4HANA Sizing Reports
▪ Goal: Migrate ECC or BW system to S/4HANA or BW/4HANA
Delta Sizing
▪ Tools:
− SAP system monitors
− Sizing Guidelines, Quick Sizer for additional load
▪ Goal: Extend an existing system by new functions
− e.g., you are live with SAP S/4HANA and want to add SAP EWM
or SAP S/4HANA embedded analytics
Not applicable
Expert Sizing
Large or complex projects
▪ Additional guidelines
▪ Custom calculations
▪ Analysis of custom coding
▪ Custom sizing guidelines

7
PUBLIC
Four-party collaboration model
Sizing is the joint responsibility of
customer (LoB), SAP, HW Vendor
and Service Provider.
They have to make sure that SAP
software runs smoothly at
customer site and that customers
don’t run into performance or
TCO issues due to under-sized or
over-sized HW.
Examples:
▪ Custom coding
▪ Different businesses require
different sizings
▪ Different applications need
different amounts of CPUs
▪ Additional needs might come from
additional not sized usages
Contributions
▪ Certified benchmarks
→ scalable hardware
▪ Different configurations
together with partners
▪ Service level
agreements
▪ Final responsibility for
sizing at customer site
if conducted by them
Expectations
▪ Optimal performance
▪ Suggestion for HW
config.
Contributions
▪ Response time and
throughput
requirements
▪ Provides business
input
Contributions
▪ Development and
provision of benchmark
toolkits
▪ Regression testing for
new releases
▪ Standard sizing
guidelines
▪ Sizing verification
processes
Hardware vendors Customer
SAP
Sizing
Recommendation
▪ CPU (SAPS)
▪ Memory (GB)
▪ Database space (GB)
▪ Disk I/O op. per sec
▪ Frontend bandwidth
Contributions
▪ Support customer in
setting up landscapes
▪ Helps to translate
business into hardware
requirements
Service Provider

8
PUBLIC
Risks in a Sizing Project
 Challenge to obtain sufficient usage information as sizing input
 Often caused by communication issues
 Insufficient sizing input is compensated by assumptions,
which should be documented
INCOMPLETE INPUT
DATA
 While it is perfectly ok to work with assumptions you must
ensure that a verification process is included in the project
plan
ASSUMPTIONS ARE
NOT VERIFIED
 Are very hard to predict: Make sure there is a verification
process
 Make sizing measurements, if required
CUSTOM CODING &
SPECIAL DATA
CONSTELLATIONS
Risks
in
a
Sizing
Project

9
PUBLIC
Sizing SAP HANA
Wrap-up
Agenda

10
PUBLIC
Official SAP Sizing Page www.sap.com/sizing
Guidelines
 Access Sizing Guidelines
 Access Sizing-related Materials
Tools
 Access Quick Sizer *
 Sizing Decision tree
 Others
Training opportunities
FAQs
* Requires login credentials

11
PUBLIC
Initial Calculation Method
Educated guess
Questionnaire
without formulas
For structured questions
T-Shirt Sizing
Simple algorithms with
many assumptions
Formulas
Simple or more
complex
Standard Sizing Methods and Tools
Quick Sizer
Supports user-
based and
throughput-based
sizing

12
PUBLIC
Finding the correct sizing tools
Quick Sizer, SAP’s online sizing tool
▪ Structured sizing questionnaires
▪ Input for
– Greenfield sizing & Delta Sizing
– GoingLive Check
▪ Hardware vendor contact list
▪ Available online since 1996
▪ Three Quick Sizer versions available: HANA-based, HANA-based Cloud, Non-
HANA-based
▪ Free of charge
▪ As of 2021: avg. 20,000 new projects per year
Characteristics
Facts and Figures
Scope
▪ SAP Key applications
– SAP S/4HANA
– SAP HANA Platform
– SAP BW/4HANA
– etc.
▪ Sizing by users and/or by throughput

13
PUBLIC
4
3
2
1
Example: Greenfield Sizing with Quick Sizer
Check the list of certified AnyDB or HANA hardware to see which
hardware providers offer hardware configurations that match the sizing
result.
Provide the sizing result (or the Quick Sizer project number) to the
hardware vendor and get proposal for appropriate hardware
configuration and prices.
The Quick Sizer tool calculates the sizing result based on the input
Create a Quick Sizer project and provide input on the business
usage/requirements of the customer into the Quick Sizer project.

14
PUBLIC
Sizing SAP HANA
Wrap-up
Agenda

15
PUBLIC
Finding the correct sizing approach
Greenfield, Bluefield (flavor of Brownfield) and (real) Brownfield Sizing
Customer needs to size systems
running on SAP S/4HANA / BW/4HANA
Net new SAP S/4HANA application
Existing SAP system fully
converted to SAP S/4HANA / BW/4HANA
New Implementation approach
“Greenfield Sizing”
Re-Implementation with Selective
transactional Data
"Bluefield Sizing“ *
Find deployment options:
Connect with hardware vendor and check for
configuration
Certified and Supported SAP HANA®
Hardware Directory
Link:
Existing SAP system converted to SAP
S/4HANA via Selective Data Transition
System Conversion approach
"Brownfield Sizing"
Use SAP HANA-based Quick
Sizer / Sizing Guidelines
Use Sizing Reports/ Procedure
(Notes: 1872170, 2296290)
* Special case - Shell copy: Re-implementation without transactional data, but with old customizing and master data

17
PUBLIC
Methodology and sizing result
• Structured questionnaires for key
SAP applications
• Sizing results given in SAPS (CPU),
GiB (Memory and disk) and disk I/O
• Optional: Memory for persistent
Memory (NVRAM)
Sizing SAP HANA
Greenfield sizing – Sizing of new applications
New SAP HANA system
(Greenfield sizing)
Use Quick Sizer
• SAP HANA version
• SAP S/4HANA Cloud version
Sizing guidelines
Expert sizing for SAP
HANA native
Services
• Request MAXAttention Service
or Sizing Service from
Consulting
Sizing document
• Overview about architecture and
functionalities for selected business
scenarios
• Sizing results given as T-Shirt
categories in SAPS (CPU) and GiB
(Memory & disk)

18
PUBLIC
Demo
Quick Sizer

20
PUBLIC
This input field 'System Business Startup time' shows the time until the database is usable for
business processes.
SAP HANA requires adequate I/O performance.
The system business startup time influences the calculation of the disk I/O requirements.
Sizing SAP HANA
SAP HANA Quick Sizer: System Business Startup Time for Disk I/O Calculation

21
PUBLIC
Result for default business system startup time (30 minutes) – Data I/O category S
Result for shorter business system startup time (10 minutes) – Data I/O category M
Sizing SAP HANA
SAP HANA Quick Sizer: Example for Different System Business Startup Times

22
PUBLIC
System lifetime refers to the lifecycle of a system from deployment to retirement.
On the project and input questionnaires 'System lifetime' can be inserted, default value is 36 months.
Sizing SAP HANA
SAP HANA Quick Sizer: System Lifetime

23
PUBLIC
Result for default system lifetime (36 months, growth rate 5 %)
Result for longer system lifetime (60 months, growth rate 5 %) – increased results for memory and
disk
Sizing SAP HANA
SAP HANA Quick Sizer: Example for Different System Lifetimes

24
PUBLIC
Sizing SAP HANA
SAP HANA Quick Sizer: Sizing SAP Fiori Frontend Server
SAP Fiori Launchpad (FLP) Logon is the most influencing sizing factor
Determine Your FLP Logon Scenario for FES Sizing
▪ The total resource consumption has two parts, the one on the SAP Fiori Front-End Server, and the other one
on the SAP S/4HANA Back End
▪ For Fiori Front-End Server Sizing, please use the SAP Fiori Front-End Server Sizing” in the Quick Sizer and
estimate the maximal number of FLP logons per hour at peak time
Please Don’t Forget to Size the Back-End for Your Application Areas

25
PUBLIC
Sizing SAP HANA
SAP HANA Quick Sizer: Sizing SAP S/4HANA Embedded Analytics
The goal of sizing for Sizing SAP S/4HANA Embedded Analytics is:
▪ To determine how many CPU cores/threads and memory are required for the processing of target
number of parallel queries (without index support)
▪ And at the same time achieving the average target response time
▪ With the HANA Quick Sizer, you can conduct a sizing for analytical apps now

26
PUBLIC
Sizing SAP HANA
SAP S/4HANA Embedded Analytics sizing has been implemented in the SAP HANA Quick Sizer
Greenfield for new
small systems
Greenfield for new
large systems
Brownfield for new
small systems
Brownfield for new
large systems

27
PUBLIC
Sizing SAP HANA
Sizing SAP S/4HANA Embedded Analytics - Greenfield
If the limit of 500 million table lines is exceeded, you’ll get an error message:
You have the chance to define the query response times and the degree of parallelization by setting
assumptions.
SAP Note 2815376
Greenfield sizing for SAP
S/4HANA embedded analytics
In this case, you can conduct an SAP S/4HANA embedded analytics sizing with table 2. Quick Sizer is not
calculating with fix response times and parallelization degrees
Quick Sizer will calculate a result, if the limit of 500
million table lines in the biggest table is not
exceeded!

28
PUBLIC
Sizing SAP HANA
Sizing SAP S/4HANA Embedded Analytics - Brownfield
If the limit of 500 million table lines is exceeded, you’ll get an error message:
You have the chance
▪ to define the query response times, degree of parallelization and the memory per query by setting
assumptions.
▪ to conduct own measurements (expert sizing). By measuring the memory per query, response times and
calculating the parallelization degree, you can enter the measured values into table 2.
SAP Note 2813738
Brownfield sizing for SAP
S/4HANA embedded analytics
In this case, you can conduct an SAP S/4HANA embedded analytics sizing with table 2.
Quick Sizer will calculate a result, if the limit of 500
million table lines in the biggest table is not exceeded!

How to Size SAP
S/4HANA Cloud?

30
PUBLIC
What is different if an application is running in the cloud?
▪ The sizing stakeholders have changed in the cloud
– Hardware vendor (on-premise) vs. SAP as system provider or any other IaaS provider
▪ If an application is running in the cloud, SAP/IaaS provider is operating the application
▪ Cloud customers are interested in how much they have to pay
However, a sizing procedure/guideline/information is still required!
▪ SAP can determine the resources required by an application within the customer's business context
▪ The infrastructure costs in a cloud environment are covered by SAP; if the hardware price per user is
underestimated, it has a direct impact on SAP's profit (TCO calculation)
Sizing
Why is sizing in the cloud important?

31
PUBLIC
SAP is responsible for providing resources that fit the customer’s business requirements
▪ SAP S/4HANA Public Cloud: The expected business input will be entered in the HANA-based Cloud Quick
Sizer for new customers
– The tool will give customers an indication about the required HANA memory and serves internally as input
for the system provisioning (tenant size)
Sizing
Why is sizing in the cloud important?

33
PUBLIC
Sizing SAP HANA
Brownfield Sizing - Migration sizing Part 1/2
Existing NW ABAP system to be
migrated to SAP HANA
SAP Notes 1872170; 1793345
SAP S/4HANA SAP BW/4HANA
SAP Note 2296290
Methodology and result
• Sizing report (note 1872170) which runs on the source anyDB ABAP
system to determine the required HANA RAM and disk
• Potential areas for housekeeping, cleanup and archiving
• It contains enhancement for persistent memory sizing
• CPU sizing is now included
Methodology and result
• Sizing report (note 229690) which runs on the source anyDB
BW ABAP system to determine the required HANA RAM and
disk
• Potential areas for housekeeping, cleanup and archiving
• In addition, a HANA CPU requirement assessment is included
• Persistent Memory configurations are taken into account

34
PUBLIC
Sizing SAP HANA
Sizing Report for SAP S/4HANA
Report /SDF/HDB_SIZING
▪ Described in SAP Note 1872170 – Suite on HANA sizing report
Scope
▪ Runs on SAP_BASIS 620 and higher
▪ Is suitable for sizing of all Business Suite products (ERP, CRM, SCM, SRM, etc.)
▪ Not suitable for BW (Refer to SAP Note 2296290 – New Sizing Report for SAP BW/4HANA)
Functionality
▪ Considers SAP S/4HANA data model changes in FI, SD, MM, ML, etc.
▪ Estimates the maximum memory consumption of the database, if migrated to SAP HANA
▪ Is independent of the source database provider
▪ Considers distribution of tables to row and column store
▪ Considers differences for secondary indexes
▪ Considers compression of legacy database
▪ Considers data aging for technical objects

35
PUBLIC
Results of Sizing Report /SDF/HDB_SIZING
The sizing report includes the sizing projections, based on the actual table sizes in the legacy system as well
as an estimation of how much the memory footprint can be reduced using functionalities that SAP HANA will
enable.

36
PUBLIC
Sizing SAP HANA
Results of Sizing Report /SDF/HDB_SIZING
The sizing report includes the sizing projections, based on the actual table sizes in the legacy
system as well as an estimation of how much the memory footprint can be reduced using
functionalities that HANA will enable.

37
PUBLIC
The sizing report /SDF/SAP HANA_BW_SIZING is a convenient method to estimate the memory
requirements of a BW system after migration to SAP HANA. Major advantages of the ABAP report:
▪ Easy to deploy and use – no DB administrator required
▪ Independent of source database specific compression and data representation
▪ Considers user defined future growth and leverages BW semantic information
The report requires ST-PI 2008_1_7xx SP12 or ST-PI 740 SP1 and SAP NetWeaver BW 7.0 SP 4 or higher.
Updated versions can be obtained from SAP Note 2296290.
Important note for DB2 on iSeries (AS/400): Please implement SAP Note 1677958!
Sizing Report for SAP BW/4HANA
Mission statement
Provide an easy to use, source database independent tool to predict resource requirements for a
BW system on an SAP HANA database.

38
PUBLIC
Sizing SAP HANA
Brownfield Sizing - Migration sizing Part 2/2
Existing Non-NW-based system to be
migrated to SAP HANA
•Analysis of legacy
system
•SAP HANA version
of Quick Sizer
SAP S/4HANA
SAP HANA native
•Analysis of legacy
system
•SAP Note 1514966
•Request a sizing
service
Existing NW Java system to be migrated
to SAP HANA
Expert Sizing
Sizing Guidelines

40
PUBLIC
Sizing Verification
Existing SAP HANA System
Non-NW products
on SAP HANA
SAP Note
1872170
SAP Business
Suite powered by
HANA & SAP
S/4HANA
Industry
Solutions
powered by SAP
HANA
SAP NW BW
powered by
HANA &
BW/4HANA
SAP Note
2296290
Early Watch
Alert
SAP Note
1969700
SAP Note
1698281

42
PUBLIC
Deployment options
Virtualization – 1788665 - SAP HANA Support for virtualized / partitioned (multi-tenant) environments
Infrastructure as a Service (IaaS) – 1380654 - SAP support in IaaS environments
Physical server – Certified and supported SAP HANA directory

43
PUBLIC
Sizing SAP HANA
Wrap-up
Agenda

44
PUBLIC
Sizing, Scalability and Benchmarks
▪ Scalable software is a pre-requisite for sizing
▪ Definition of SAPS is derived from the Sales
& Distribution (SD) Benchmark
▪ Expert sizing is recommended for custom
development
Customer
▪ The success of the sizing exercise almost
entirely depends on the quality of the
customer input data
▪ Sizing involves very different people and
teams within an organization
Sizing …
▪ …means translating business
requirements into hardware requirements
▪ …is an iterative process
▪ …is not configuration
HANA Sizing…
▪ …approach is different from the sizing of
traditional database
▪ …in case of greenfield should be done
with the HANA Quick Sizer
▪ …in case of migrations should be done
with the corresponding sizing reports
Sizing
Summary and key takeaways

45
PUBLIC
www.sap.com/sizing
▪ Access to Quick Sizer
▪ Access to sizing guidelines, for example, SAP HANA accelerators
SAP Support Portal
▪ SAP Note 1872170 – SAP S/4HANA memory sizing
▪ SAP Note 1793345 – Sizing for Suite on HANA
▪ SAP Note 2296290 - New Sizing Report for BW/4HANA
▪ SAP Note 1969700 - SQL Statement Collection for SAP HANA
▪ SAP Note 1698281 - Assess the memory consumption of a SAP HANA System
▪ SAP Note 1514966 – SAP HANA: Sizing SAP In-Memory Database
▪ SAP Note 2779240 - Workload-based sizing for virtualized environments
▪ SAP Note 2815376 - Greenfield sizing for SAP S/4HANA embedded analytics
▪ SAP Note 2813738 - Brownfield sizing for SAP S/4HANA embedded analytics
▪ SAP Note 1380654 - SAP support in IaaS environments
▪ SAP Note 2786237 - Sizing SAP HANA with Persistent Memory
SAP HANA Quick Sizer (for greenfield sizing)
YouTube Video
Sizing information and tools
Sources of published sizing documentation

Contact information:
Sebastian Schmitt
SAP SE
Product Management
sebastian.schmitt@sap.com
Cell: +49 151 18874932
Thank you.

© 2022 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/copyright for additional trademark information and notices.
www.sap.com/contactsap
Follow us

Principles of SAP HANA Sizing - on premise and cloud-1.pdf

More Related Content

What's hot (20)

Similar to Principles of SAP HANA Sizing - on premise and cloud-1.pdf (20)

Recently uploaded (20)

Principles of SAP HANA Sizing - on premise and cloud-1.pdf