Database Reference
In-Depth Information
• Customers can compare the SAPS value generated by the Quick Sizer project with the
benchmark numbers published by SAP for different vendors and server configura-
tions.
• Different types of sizing are available based on the stage of the SAP project, from
blueprint to post go-live and upgrade stages.
• Resizing is done when load is added to the system.
• Resizing is done by gathering data from different SAP monitors.
• Delta sizing is done when new functionality is added to the project.
• Upgrade sizing is done for SAP upgrade projects, and usually SAP provides an OSS
Note on the impact of the upgrade for system resources.
• T-shirt sizing is used for newly developed solutions.
• Network sizing can be performed by using a SAP-provided formula.
• Common SAP sizing project pitfalls are use of inexperienced resources to perform siz-
ing, incorrect interpretation of the sizing elements, and mistakes in choosing the peak
load volume and period in the Quick Sizer.
• Common pitfalls can be mitigated by assigning an experienced SAP sizing consultant
to work closely with the business teams in arriving at accurate SAP sizing numbers.
• The hardware vendor is ultimately responsible for providing a scalable hardware solu-
tion to its customers.
Additional Resources
•
Sizing decision tree
https://websmp209.sap-ag.de/~sapidb/
011000358700000970192010E/ebene1.htm (An S user account is required to log in to
the SAP Service Marketplace.)
•
SAP benchmark
www.sap.com/solutions/benchmark/index.epx
•
SAP benchmark results interpretation
www.sap.com/solutions/benchmark/ben-
chresults/benchresults.html
•
SAP benchmark glossary
www.sap.com/solutions/benchmark/glossary.epx
