SAPFree calculatorPDF, Excel, Word exportSAP Business OneAll SAP Business One tools

SAP Business One HANA Server Memory Sizing Calculator

This calculator estimates the memory a SAP Business One version for SAP HANA server needs for your company databases, growth and concurrent users. Every factor is an input, so you can replace the defaults with values measured after a test migration.

Your numbers

GB

Per company. SQL Server data file size, or the schema size in HANA Studio if already on HANA.

Include test companies that stay on the production server.

%
3 years
GB

Service Layer, analytics and session overhead. An assumption: adjust after measuring.

HANA column store compresses data. Measure after a test migration; 1.0 if already on HANA.

Rule of thumb: HANA needs about twice the data footprint for processing.

Your results

Estimated memory needed
169.24
GB, including a 16 GB reserve for OS and services.
Future data footprint in HANA
69.12
GB.
Memory for data and working space
138.24
GB.
Memory for users and services
15
GB.
Recommended RAM (64 GB steps)
192
GB.

Rule-of-thumb estimate with every factor exposed as an input. The official sources are the SAP Business One version for SAP HANA hardware requirements and sizing guides on help.sap.com; certified hardware and your partner's sizing take precedence.

Save results:

Estimated HANA memory vs years ahead

Sweeps Years ahead from 1 to 7, holding your other inputs fixed.

Get your Business One HANA sizing checked

Send your company database sizes, users and growth plans and we will return a reviewed memory estimate and questions for your hardware vendor.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Enter the size of a typical company database and the number of companies on the server, including any test or demo companies kept on production. If you are moving from SQL Server, set the compression factor; if you are already on HANA, set it to 1.0 and enter the in-memory size. Set growth and years ahead, then concurrent users and memory per user. The primary output adds data and working space, user and service memory and a 16 GB reserve for the operating system and Business One services, then rounds up to a 64 GB step because servers are bought in memory steps. The chart shows how the requirement rises over the years ahead.

  • Count every company schema on the HANA instance
  • Include attachments only if they are stored in the database
  • Re-run after the test migration with measured compression

Where the factors come from

SAP publishes the hardware requirements guide and sizing guide for SAP Business One version for SAP HANA on help.sap.com; those, and the certified hardware directory, are the official sources and take precedence over this estimate. The factors here are planning assumptions. HANA's column store compresses most Business One tables well compared with SQL Server row storage, but the ratio varies with data, so measure it. HANA also needs working memory beyond the stored data for joins, sorts, delta merges and analytics, which is why a factor of around 2 is a common rule of thumb. Service Layer, the analytics features and Web Client add per-session memory. The 16 GB reserve covers the operating system and server components.

  • Official: SAP Business One HANA hardware requirements and sizing guides
  • Hardware must be SAP-certified for HANA (appliance or supported TDI setup)
  • Factors are inputs, not SAP values

Worked example

Two companies of 40 GB on SQL Server growing 20 percent a year, sized for 3 years: 80 GB x 1.2^3 = 138 GB on SQL Server, which at a 0.5 compression factor is about 69 GB in HANA. Doubling for working space gives 138 GB. Thirty concurrent users at 0.5 GB add 15 GB, plus the 16 GB reserve, for about 169 GB. Rounded up to a 64 GB step that is 192 GB. Moving to 5 years ahead lifts it to about 230 GB, so 256 GB. If a third company is likely, add it now: RAM is cheaper at purchase than as a later upgrade.

SQL Server versus HANA and gotchas

On Microsoft SQL Server, Business One runs with far less RAM because data lives on disk and SQL Server caches what it needs; the SQL Server requirements are in the same SAP hardware guide. On HANA the whole data set is in memory, so memory is the main sizing driver. Common mistakes: forgetting test companies, sizing on the SQL Server backup size rather than data size, ignoring growth from add-ons with large user-defined tables, and running other software on the HANA host. After go-live, check actual memory use with HANA Studio or the M_SERVICE_MEMORY view and compare it with this estimate.

Frequently Asked Questions

Is there an official SAP Business One HANA sizing tool?

SAP provides the hardware requirements guide and sizing guide for SAP Business One version for SAP HANA on help.sap.com, and partners use them with the customer's data. This calculator is a transparent estimate to plan budgets and compare scenarios before that formal sizing.

How much RAM does SAP Business One on HANA need?

It depends on the total size of all company databases after compression, growth and the number of users. Small single-company systems need far less than multi-company systems with years of history. Use measured database sizes, then confirm against the SAP sizing guide and certified hardware options.

What are the SAP Business One SQL Server requirements?

The SQL Server version, edition and hardware requirements are in the SAP Business One hardware requirements guide and the platform support documentation for your release. SQL Server needs much less memory than HANA for the same data, but it does not offer the HANA-only analytics features.

Can I install SAP Business One HANA on any server?

HANA must run on SAP-certified hardware or a supported tailored datacenter setup with a supported Linux operating system. Check the certified hardware directory and the release's platform support documentation before purchasing a server.

If you want Business One users to ask questions of their HANA data in plain English on your own server, we can add a private AI layer alongside it.

ArchRay builder
Design the on-prem AI stack for SAP Business One: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

AI on your ERP

Integrations

Comparisons

Software