Topic · SAP HANA Database Licensing

Memory is the meter.

SAP HANA is licensed by memory, in 64GB blocks, in Runtime or Full-Use tiers. The tier governs the use-case scope. The use-case scope governs the audit finding. The dual-purpose data is the exposure.

The In-Memory DatabaseRuntime, Full-Use, or both — the tier governs everything that follows.

Section I · The Landscape

Two tiers, one auditable database.

SAP HANA is the in-memory database underneath S/4HANA, BW/4HANA, and an expanding catalogue of SAP applications. It is licensed by memory consumption in 64GB blocks, with two principal entitlement tiers that govern what the database is permitted to do.

Runtime HANA is restricted to the licensed SAP application above it. It is sized as a percentage of the SAV — the Software Application Value — of the application it supports, and may not be used for non-SAP data. Full-Use HANA is unrestricted and may serve any workload, but is priced per 64GB block at the higher tier.

The audit surface in HANA is the gap between the licensed tier and the actual use. A Runtime entitlement holding custom-application data, BI extracts from non-SAP sources, or analytics dashboards beyond the licensed application is a documented tier violation. The remediation invoice is the difference between Runtime and Full-Use across the licensed memory.

The defensible HANA posture combines a documented use-case map, a memory-consumption baseline, and an audit-defensible separation between the licensed application data and everything else. We work the HANA estate from the entitlement letter outward.

Section II · The Risk Surface

Eight tier violations.

— I.

Dual-Purpose Use

Non-SAP data loaded into a Runtime HANA instance is a documented tier violation, remediated by full-use repricing of the affected memory.

— II.

Side-Car Analytics

BI dashboards, custom analytics applications, and reporting tools reading from Runtime HANA outside the licensed application scope.

— III.

Memory Consumption Drift

Memory grows organically through data accumulation, in-memory indexes, and column-store growth. The licensed block count becomes the floor.

— IV.

Archival Lag

Cold and historical data left in memory consumes licensed capacity and inflates the next measurement against the licensed block count.

— V.

SAV-Linked Sizing

Runtime HANA is sized as a percentage of application SAV. SAV growth from upstream changes drives downstream HANA exposure.

— VI.

Embedded Entitlement Misuse

Some applications include an embedded HANA entitlement. Using it for unrelated workloads is the classic dual-purpose audit finding.

— VII.

Non-Production Instance Counts

Sandbox, dev, and test HANA instances often need to be licensed depending on the contract. The free-tier assumption is the exposure.

— VIII.

Cloud Migration Repricing

Migrating HANA into a cloud or RISE estate frequently re-tiers the entitlement. The repricing event is the negotiation.

— Field Note · HANA Tier Audit

The dual-purpose database that nearly tripled in price.

A pharmaceutical group was issued a HANA audit finding for nine point four million dollars, driven by Runtime HANA holding non-SAP master data, side-car analytics applications reading from the database, and a sandbox instance counted against the production entitlement.

We rebuilt the use-case map across the HANA estate. We separated the SAP application workload from the non-SAP analytics workload and proposed a discrete Full-Use carve-out for the latter. We negotiated the dual-purpose finding into a contained capacity uplift and rewrote the entitlement letter for the remaining term.

Read the case file →

Finding

$9.4M

HANA dual-purpose claim

Settled

$2.3M

capacity uplift with new entitlement letter

Reduction

76%

below opening audit claim

Renewal

-24%

three-year carve-out negotiated

Questions, frequently.

How is SAP HANA licensed?

By memory consumption, with two principal entitlement tiers: Runtime (restricted to the licensed application, sized as a percentage of SAV) and Full-Use (priced per 64GB block, usable for any workload). The metric, the tier, and the use-case scope are all audit-material.

What is the difference between Runtime and Full-Use HANA?

Runtime HANA is restricted to use as the database for the licensed SAP application above it. Full-Use HANA can serve any workload, including custom applications. Putting non-SAP data into a Runtime HANA instance is a documented audit finding.

Why does HANA create audit exposure?

Because memory consumption grows organically. Data archival lags. Side-car analytics applications get attached. Dual-purpose use creeps in. Each of those is a tier-violation event and each is monetised at the audit.

Do non-production HANA instances need to be licensed?

It depends on the contract. Some agreements include sandbox and development capacity within the production entitlement; others meter every instance separately. The free-tier assumption is the most common exposure source.

How does RISE migration affect HANA licensing?

RISE typically subsumes the HANA entitlement into the bundled subscription, which re-tiers and re-prices the database against the new contract. The migration moment is a major negotiation event with multi-year implications.