TL;DR
Get audio and creator 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 data center capacity ledger. The company says its connections are read-only and reports tests on a simulated landscape of 200 hosts; it has not provided customer deployment results.
Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting and replication takeover checks to its data center capacity ledger, as described in the original analysis. The early-access software is aimed at SAP hosting providers and operations teams, but the company’s reported test results come from a simulated landscape, not a customer deployment.
The release breaks each HANA host’s physical memory into categories: an operating-system reserve, memory used by HANA systems, allocated but unused memory, capacity held for replicas from other sites, and remaining free memory. Rymvard sets the default operating-system reserve at 10% of the first 64 GiB and 3% of memory above that amount, unless a host has a different reserve configured. System usage is calculated from its 30-day peak. If allocations exceed physical memory, the ledger shows overbooking rather than presenting the result as negative free capacity.
For systems using HANA system replication, the software checks whether a secondary host could accommodate the primary system’s allocation after a takeover. It can count named test or development systems as stoppable, but does not treat other customers’ production systems as stoppable. Results are reported as a fit, a fit after named systems are stopped, a shortfall measured in GiB, or an unknown status. A replication status more than one hour old, or a memory reading more than 24 hours old, produces an unknown rather than a passing result. Scale-out systems are evaluated 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 quarterly memory runway by site, weighting planned go-lives by their probability. A new SAP Operations workspace highlights free HANA memory, production systems without replication, takeovers that would fail, and hosts above 90% utilization. Rymvard says HANA instances are mirrored into its compute view so their memory can appear in customer showback and lifecycle planning.
🔍 Read the full analysis: Rymvard Brings SAP HANA Memory Into The Data Center Capacity Ledger on Rymvard
Making HANA Failover Capacity Visible
The new ledger addresses a specific planning problem for providers: memory can be the constraint even when a data center has room in its broader infrastructure. A HANA host may lack capacity for a proposed system, or a replication partner may be unable to take over if a primary system fails. Showing overbooking and takeover shortfalls separately could help operations teams identify those limits before placement decisions or a failover.
The value of those views depends on the quality and freshness of the input data. Rymvard’s rule that stale measurements yield an unknown status avoids treating old information as evidence that capacity is available. Placement proposals and quarterly runway estimates may help teams compare planned deployments across sites, but the release materials do not establish cost savings, better reliability or other customer outcomes.
For potential users, the distinction between demonstrated product behavior and expected operational benefit matters. The announced features and simulated checks describe how the release is intended to work; they do not establish performance across live customer landscapes, unusual configurations or changing workloads.
SAP HANA memory monitoring 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 SAP Host Agent over HTTPS and permits 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 product can also read system, customer and environment information through read-only interfaces in SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa. The release names these as supported sources; it does not say that customers must connect all of them.
Rymvard says it tested version 0.23 against a simulated estate containing 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, it 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 screens use an illustrative estate and do not represent a customer, site or real outcome.
“Nothing is ever written to SAP.”
— Rymvard
Customer Results Are Not Yet Available
Rymvard describes version 0.23 as early-access software and has not identified a customer deployment or supplied customer outcomes for this release. Its published test figures come from a simulated landscape, so they do not show how the product performs across real-world SAP environments. The materials also do not provide an independent evaluation.
The company has not published prices, saying terms are arranged with early-access partners. It has not detailed how the software handles every SAP configuration, how integrations are validated in each environment, or how frequently readings update beyond the stated stale-data thresholds. Those limits leave the practical performance and suitability of the release for individual estates unconfirmed.
Early-Access Evaluations Continue
The next step is evaluation with early-access partners, with pricing negotiated directly with Rymvard. The company has not announced a broader availability date, public pricing or a named customer deployment. Further evidence about live performance, configuration coverage and operational outcomes will depend on information Rymvard or participating customers choose 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 with HANA operations indicators.
Was the release tested in a customer data center?
No customer deployment is identified in the release information. Rymvard reports tests on a simulated landscape with 200 HANA hosts, 161 systems and 39 replicated pairs.
Does the software write to SAP systems?
Rymvard says its SAP connections are read-only and states that it does not write to SAP. The described Host Agent operations and monitoring queries are reads.
When does the ledger mark a takeover result as unknown?
It reports an unknown status if replication information is more than one hour old or a memory figure is more than 24 hours old. It also reports unknown when it cannot determine whether capacity is sufficient.
When will the software be generally available, and what will it cost?
Rymvard has not announced a general availability date or public price list. The release is in early access, with terms arranged directly with partners.
Primary source: Rymvard · via ThorstenMeyerAI.com
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
