TL;DR
Get monitors, keyboards and dev gear 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 memory accounting, placement proposals and replication takeover checks to its capacity ledger. The company tested the early-access release against a simulated landscape, not a customer deployment, and has not reported real-world outcomes.
Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting, host-placement proposals and replication takeover checks to its data center capacity ledger, as described in the original analysis. The early-access release is aimed at SAP hosting providers and operations teams, but the test results Rymvard disclosed came from a simulated estate rather than a customer deployment.
The new ledger breaks down memory on each HANA host into operating-system reserve, memory used by HANA systems, allocated but unused memory, capacity reserved for replicas from other sites, and remaining free memory. By default, it reserves 10% of the first 64 GiB and 3% of memory beyond that, unless a host has a different reserve configured. System usage is based on its 30-day peak. If allocations exceed physical memory, the ledger shows overbooking rather than presenting a negative free-capacity figure.
For systems using HANA system replication, Rymvard checks whether the secondary host could accommodate the primary system’s allocation during a takeover. Its results can say that the takeover fits, fits after named systems are stopped, does not fit with a shortfall in GiB, or is unknown. A production system belonging to another customer is not treated as stoppable. If replication status is more than an hour old, or a memory reading is more than 24 hours old, the result is unknown rather than a pass. Scale-out systems are assessed as a whole, using 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, weighting planned go-lives by 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, 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 release focuses on a planning constraint that can be obscured by broader data center capacity figures: available infrastructure does not necessarily mean available HANA memory. A site may have room in its wider facilities while a particular host—or a replication partner—cannot accommodate an allocation. Showing overbooking and takeover shortfalls separately could help operators identify those limits before placing a system or relying on a failover.
The value of the checks depends on the quality and freshness of the underlying information. Rymvard’s use of an unknown result for stale measurements avoids treating old data as proof that capacity is available. Its placement proposals and quarterly runway estimates could help teams compare planned deployments with site capacity, but the release does not establish customer savings, improved reliability or operational outcomes. Those remain to be demonstrated in real deployments.
For providers and operations teams considering the product, the distinction between a simulated test and live customer use is material. The announced rules describe how the software is intended to work; they do not show how it performs across real landscapes, unusual SAP configurations or changing workloads.
SAP HANA memory management software
As an affiliate, we earn on qualifying purchases.
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 the software does not write to SAP.
The release also names read-only connections to SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa as sources of system, customer and environment information. Rymvard presents these as supported sources; it does not say that all are required together.
For its disclosed test, Rymvard used a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, the software identified one production system without replication, one takeover short by 512 GiB, one host overbooked by 128 GiB, and one replication in an error state. The company 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
data center capacity planning tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Rymvard describes version 0.23 as early-access software. It has not identified a customer deployment or provided customer outcomes for this release; the published test figures come from a simulation. The company also has not published prices, saying terms are arranged with early-access partners.
The release does not provide independent evaluations or evidence of performance across live customer environments. It also leaves open how the software handles every SAP configuration, how each integration is validated in a particular environment, and how readings update beyond the stated age thresholds. The disclosed test results show what the software reported in one simulated scenario, not how it will perform under real-world workload changes.
HANA system replication monitoring tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Partner Evaluations Set the Next Step
The immediate next step is evaluation by Rymvard’s early-access partners, with pricing arranged directly with the company. Rymvard has not announced a wider availability date, a public price list or a named customer for version 0.23. Further evidence about live deployments, customer outcomes and behavior across different SAP environments would be needed to judge how the new accounting and takeover checks perform in practice.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA memory accounting, placement proposals, replication takeover checks, site-level memory runway estimates and an SAP Operations workspace to its capacity ledger.
Has Rymvard tested the release with a customer?
The disclosed results came from a simulated landscape of 200 hosts, 161 systems and 39 replicated pairs. Rymvard has not identified a customer deployment or published customer outcomes for this release.
How does the ledger report a possible replication takeover?
It reports whether the secondary host can accommodate the primary system, including whether the fit depends on stopping named systems. It can also report a shortfall or return unknown when replication or memory data is too old.
Does Rymvard write data to SAP?
Rymvard says its SAP connections are read-only and states, “Nothing is ever written to SAP.” The release lists specific Host Agent operations and monitoring queries used by the collector.
When will the software be generally available?
Rymvard has not announced a broader availability date. Version 0.23 is described as early access, with evaluation by partners as the next step.
Primary source: Rymvard · via ThorstenMeyerAI.com
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
