TL;DR
Get everyday essentials 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 tested the early-access software on a simulated landscape, not a customer deployment, and has not reported customer outcomes.
Rymvard released version 0.23 of its early-access data center capacity ledger on October 4, adding SAP HANA memory accounting, system placement proposals and replication takeover checks, as described in the original analysis. The release is aimed at SAP hosting providers and operations teams, but the company’s reported tests used a simulated environment rather than a customer deployment.
The software breaks down each HANA host’s physical memory into an operating-system reserve, memory in use, allocated but unused memory, replica reservations and free capacity. Its default 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. When allocations exceed physical memory, the ledger identifies overbooking rather than representing free memory as a negative figure.
For systems using HANA system replication, the release checks whether a secondary host could accommodate the primary system’s allocation after takeover. It returns one of four statuses: fits, fits after stopping named systems, does not fit, or unknown. A shortfall is reported in GiB. Named test or development systems may be treated as stoppable, but production systems belonging to other customers are not.
Rymvard says a replication status older than one hour, or a memory figure older than 24 hours, results in an unknown status instead of a passing result. Scale-out deployments are assessed as a whole, with the weakest host pair determining the result. The release also proposes a host and replication-site partner for a new system and estimates memory runway by site and quarter, using planned go-lives weighted by their probability.
🔍 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 capacity problem that can be obscured by broader data center totals: a facility may have room across its infrastructure while a particular HANA host or replication partner lacks the memory needed for a system or takeover. Separating available memory, overbooking and replica reservations may give operations teams a clearer view of that constraint before placing a workload or relying on failover.
The takeover checks matter because replication alone does not establish that a secondary system has enough capacity to run the primary workload. Showing a shortfall, or marking the result unknown when readings are stale, can help teams identify cases that need investigation rather than treating unverified capacity as available. Rymvard also says HANA instances are mirrored into its compute view, allowing the information to appear in customer showback and lifecycle planning.
The potential operational value is not the same as demonstrated results. The release description does not establish that the software reduces costs, improves reliability or has changed customer outcomes. Those questions depend on the accuracy of the source data, how teams use the warnings and performance in live environments.
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 uses 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 sources for landscape information: SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa. Rymvard presents these as supported sources; the release description does not say that customers must use all of them together. A new SAP Operations workspace displays free HANA memory, production systems without replication, takeovers that would fail and hosts above 90 percent utilization.
Rymvard reports testing version 0.23 against a simulated landscape with 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 one replication in an error state. The company says the screens use an illustrative estate, not a customer environment.
“Nothing is ever written to SAP.”
— Rymvard
data center capacity planning software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Live Customer Results Remain Unreported
Rymvard describes version 0.23 as early-access software and has not identified a customer deployment or provided customer outcomes for this release. Its test findings come from a simulated landscape, so they do not show how the product performs across live customer environments, unusual SAP configurations or workloads that change over time.
The release outlines specific data-age thresholds and connection limits, but does not provide independent evaluations or detail how integrations are validated in each environment. It also does not say how frequently readings update beyond the stated thresholds. Pricing is not public; Rymvard says terms are arranged with early-access partners. No broader availability date or named customer has been announced.
As an affiliate, we earn on qualifying purchases.
Early-Access Partner Evaluations
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 accounting and takeover checks work against live SAP landscapes, but Rymvard has not announced when results will be shared.
The company has also not set a date for broader availability or published a price list. Until it provides customer deployments or other real-world performance evidence, the release establishes the product’s stated functionality and simulated test scope, rather than demonstrated outcomes in production.
HANA system replication capacity check
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA memory accounting, system placement proposals and replication takeover checks to its data center capacity ledger.
Does the software write to SAP?
Rymvard says its SAP connections are read-only and states, “Nothing is ever written to SAP.”
How does the takeover check handle old data?
The result is marked unknown if replication status is more than one hour old or a memory figure is more than 24 hours old.
Was version 0.23 tested at a customer site?
No customer deployment is identified. Rymvard reports testing on a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs.
When will the product be generally available?
Rymvard has not announced a broader availability date. The stated next step is evaluation by early-access partners.
Primary source: Rymvard · via ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
