TL;DR
Get the latest gadgets 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
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 software uses read-only SAP connections, but its reported test results came from a simulated landscape, and it has not disclosed customer outcomes.
Rymvard released version 0.23 of its data center capacity ledger on October 4, adding tools to track SAP HANA memory, suggest system placements and check whether replication partners could accommodate a takeover. The early-access update targets SAP hosting providers and operations teams, but the company’s reported tests used a simulated estate, not a customer deployment.
The update breaks down physical memory on each HANA host into the operating-system reserve, memory used by HANA systems, allocated but unused capacity, memory reserved for replicas from other sites, and remaining free memory. Unless a host specifies another reserve, Rymvard applies a default of 10% of the first 64 GiB and 3% of memory above that. System usage is based on its 30-day peak. Capacity allocations that exceed physical memory are shown as overbooking rather than being hidden as negative free capacity.
For systems using HANA system replication, the ledger checks if the secondary host could accommodate the primary system’s allocation following a takeover. It reports whether the system fits, fits after named test or development systems are stopped, does not fit and by how many GiB, or has an unknown status. Rymvard says production systems belonging to other customers are not treated as stoppable. A replication status older than one hour, or a memory figure older than 24 hours, produces an unknown result instead of a passing check. Scale-out systems are assessed as a whole, based on 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 the memory figures can feed customer showback and lifecycle planning. A new SAP Operations workspace displays indicators for free HANA memory, production systems without replication, takeovers that would fail, and hosts above 90% utilization.
🔍 Read the full analysis: Rymvard Brings SAP HANA Memory Into The Data Center Capacity Ledger on Rymvard
Making HANA Failover Capacity Visible
The update addresses a capacity-planning issue for providers whose immediate constraint is memory rather than power. A data center may have room in its broader infrastructure while a specific HANA host, or the secondary host intended to take over a system, lacks enough memory for the allocation. Separating free capacity, overbooking and takeover shortfalls could help operations teams identify these constraints before placing a workload or relying on failover.
The result is a planning view, not evidence that deployments will become more reliable or less costly. Its usefulness depends on the accuracy and freshness of the underlying data, as well as how well the checks reflect each provider’s SAP landscape. Returning “unknown” when key readings are stale avoids treating old information as proof of available capacity, but the release does not report customer outcomes or quantify operational benefits.
As an affiliate, we earn on qualifying purchases.
Read-Only SAP Data Connections
Rymvard says its collector connects to the 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 these connections do not write to SAP.
The software can also read system, customer and environment details through read-only interfaces in SAP Focused Run, ServiceNow, SAP Solution Manager via its System Landscape Directory, and SAP LaMa. Rymvard describes these as supported sources for landscape information; it does not say that customers must connect all of them.
For its release testing, Rymvard used a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, the company says the software flagged one production system without replication, one takeover with a 512 GiB shortfall, one host overbooked by 128 GiB and one replication in an error state. Rymvard says the displayed screens use an illustrative estate, not a customer environment, and do not represent a real customer, site or outcome.
“Nothing is ever written to SAP.”
— Rymvard
Customer Results Remain Unreported
Rymvard describes version 0.23 as early-access software and has not identified a customer deployment or supplied customer results for the release. The simulated test results show how the checks behaved in the company’s stated scenario, but do not establish performance across live customer landscapes, unusual SAP configurations or workloads that change over time.
The release description also does not provide independent evaluation, a public price list, or detailed validation results for each integration in individual environments. Rymvard has not specified a broader availability date. The stated age thresholds explain when some data produces an unknown result, but the company has not provided further details on update speeds in customer settings.
Early-Access Evaluations Ahead
The next stated step is evaluation by early-access partners, with pricing arranged directly with Rymvard. The company has not announced named partners, a public price list or a date for wider availability. Further evidence about how the checks perform in live environments will depend on customer deployments and any results Rymvard chooses to publish.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA memory accounting, system placement proposals, replication takeover-capacity checks, and a workspace for viewing selected HANA capacity indicators.
Does the software write to SAP?
Rymvard says its SAP connections are read-only and that it does not write to SAP. The company describes Host Agent access, monitoring queries and other landscape-data connections in the release material.
Were the reported results from a live customer?
No customer deployment is identified. Rymvard says its test used a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs.
When does a takeover check return an unknown result?
According to Rymvard, the check returns unknown if the replication status is more than one hour old or a memory figure is more than 24 hours old.
When will the software be generally available?
Rymvard has not announced a broader availability date. The stated next step is evaluation by early-access partners, with commercial terms agreed directly with the company.
Primary source: Rymvard · via ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
