SAP HANA Memory Joins The Data Center Capacity Ledger With Rymvard

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get tech for your team delivered free — and shop member deals

• Fast, free delivery on millions of items
• Access to Prime Big Deal Days deals on October 6–7
• Prime Video, Amazon Music and more included

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Rymvard released version 0.23 on October 4, 2026, adding SAP HANA host-memory accounting, placement proposals and replication takeover checks to its data center capacity ledger. The company says the release was tested against a simulated landscape, not a customer deployment; real-world performance and customer outcomes have not been provided.

Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting and replication takeover checks to its data center capacity ledger. The early-access software is aimed at SAP hosting providers and operations teams, but the company’s reported test results come from a simulated estate, not a customer deployment.

The release breaks each HANA host’s physical memory into the operating-system reserve, memory used by HANA systems, allocated but unused memory, capacity reserved for replicas from other sites and remaining free capacity. Rymvard’s default operating-system reserve is 10 percent of the first 64 GiB and 3 percent of the remaining memory, unless a host has a different reserve configured. System usage is calculated from its 30-day peak. Memory allocations that exceed physical capacity are displayed as overbooking rather than being obscured as negative free memory.

For systems using SAP HANA system replication, Rymvard checks whether a secondary host could accommodate the primary system’s allocation after a takeover. It returns one of four outcomes: the workload fits; it fits after named systems are stopped; it does not fit, with a shortfall given in GiB; or the result is unknown. Named test or development systems may be treated as stoppable, but production systems belonging to other customers are not. Replication information older than an hour or memory figures older than 24 hours lead to an unknown result, not a passing assessment. For scale-out systems, the assessment uses the weakest host pair.

Version 0.23 also proposes a host and replication-site partner for a new HANA system and estimates memory runway by site and quarter, using planned go-lives weighted by their probability. Rymvard says HANA instances are mirrored into its compute view so SAP memory can inform customer showback and lifecycle planning. A new SAP Operations workspace displays free HANA memory, production systems without replication, failing takeover checks and hosts above 90 percent utilization.

Making HANA Failover Capacity Visible

The release targets a planning problem for providers where memory, rather than power or broader facility capacity, limits deployment. A data center may have room in its wider infrastructure while a particular HANA host—or the secondary host expected to take over—does not have enough memory for an allocation. Separating overbooking from free capacity and highlighting takeover shortfalls could help operations teams spot those constraints before placing a system or relying on failover.

The checks may also give providers a way to compare expected deployments with capacity at different sites. That could make quarterly planning more specific than a general view of data center resources, particularly where planned go-lives have varying probabilities. However, the release describes product functions, not demonstrated customer benefits: it does not establish that the software has reduced costs, prevented outages or improved reliability in live environments.

For users assessing the release, the distinction between reported test functionality and validated customer results is material. The usefulness of the ledger depends on the accuracy and freshness of the information it receives. Rymvard’s choice to label stale readings unknown avoids treating old data as proof of available capacity, but users still need current, correctly configured source information to make operational decisions.

Read-Only SAP Data Connections

Rymvard says its collector communicates with SAP Host Agent over HTTPS and is limited to four read operations: ListInstances, ListDatabases, GetDatabaseStatus and GetComputerSystem. A separate monitoring connection uses TLS and a fixed set of six SELECT queries, with a 60-second limit per system and no more than eight systems queried at once. The company says the product does not write to SAP.

The release also lists read-only connections for landscape details through SAP Focused Run, ServiceNow, SAP Solution Manager via its System Landscape Directory, and SAP LaMa. Rymvard presents these as supported sources; it does not say that every installation must connect all of them. The release is described as early access, with pricing arranged directly with early-access partners rather than published as a public list.

Rymvard says it tested version 0.23 against a simulated landscape containing 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, it identified one production system without replication, a takeover short by 512 GiB, a host overbooked by 128 GiB and a replication in an error state. The company says the displayed screens use an illustrative estate and do not represent a real customer, site or outcome.

“Nothing is ever written to SAP.”

— Rymvard

Customer Evidence Remains Pending

Rymvard has not identified a customer deployment or supplied customer outcomes for version 0.23. Its reported test results are from a simulated landscape, and the company says the example screens do not depict an actual customer environment. The results therefore do not show how the product performs across live SAP estates, unusual configurations or workloads that change over time.

The release describes the inputs, age thresholds and assessment rules, but it does not provide independent evaluations or real-world performance data. It is also unclear how integrations are validated for each customer environment or how frequently readings update in practice beyond the stated thresholds. Rymvard has not published a public price list or announced a general availability date.

Early-Access Evaluations Ahead

The immediate next step is evaluation by Rymvard’s early-access partners, with commercial terms arranged directly with the company. Those evaluations could provide evidence about how the memory accounting, placement proposals and takeover checks behave in live customer landscapes, but no partner names or results have been announced.

Rymvard has not given a date for broader availability. Further updates to watch for include customer deployments, evidence from operational use, details on pricing and any changes to the product’s supported SAP configurations or data-freshness rules.

Key Questions

What did Rymvard add in version 0.23?

Version 0.23 adds SAP HANA host-memory accounting, placement proposals and replication takeover checks to Rymvard’s data center capacity ledger.

Has Rymvard tested the release with a customer?

The company reports testing against a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. It has not identified a customer deployment or provided customer outcomes for the release.

How does the software treat old capacity information?

Rymvard reports an unknown result if replication status is more than an hour old or a memory figure is more than 24 hours old. It does not treat those stale readings as evidence that a takeover will fit.

Does Rymvard write data to SAP?

Rymvard says its SAP connections are read-only and states: “Nothing is ever written to SAP.”

When will the product be generally available?

No broader availability date has been announced. The release is in early access, with evaluations and pricing handled directly with partners.

Primary source: Rymvard · via ThorstenMeyerAI.com