What Rymvard’s SAP HANA Memory Means For The Capacity Ledger

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 early-access release uses read-only SAP connections, but the reported results are from a simulated landscape, not a customer deployment.

Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting, system placement proposals and replication takeover checks to its data center capacity ledger, as described in the original analysis. The early-access update is aimed at SAP hosting providers and operations teams that need to track whether hosts and replication partners have enough memory for planned systems or a failover; Rymvard’s published test results, however, come from a simulated estate, not a customer deployment.

The ledger breaks each HANA host’s physical memory into operating-system reserve, memory used by HANA systems, allocated but unused memory, capacity reserved for replicas from other sites, and memory still free. Unless a host specifies a different reserve, Rymvard sets aside 10% of the first 64 GiB and 3% of remaining memory. System usage is based on its 30-day peak. If allocations exceed physical capacity, the software shows the host as overbooked instead of disguising the excess as negative free memory.

For systems using HANA system replication, the software checks whether the secondary host could take on the primary system’s allocation. It reports whether the system fits, fits after named test or development systems stop, does not fit (with the shortfall in GiB), or has an unknown status. Production systems belonging to other customers are not counted as stoppable. A replication status older than one hour or a memory reading older than 24 hours produces an unknown result, not a passing one. 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 quarterly memory runway by site, weighting planned go-lives by probability. Rymvard says HANA instances are mirrored into its compute view for customer showback and lifecycle planning. A new SAP Operations workspace highlights free HANA memory, production systems without replication, takeovers that would fail and hosts above 90% utilization.

Making HANA Failover Capacity Visible

The update focuses on a specific planning problem: memory can be the limiting resource for an SAP system even when a data center has capacity elsewhere. A host may be overbooked, or a replication partner may lack enough memory to receive a system during a takeover. Showing those constraints separately from general infrastructure capacity could help operations teams spot placement or failover gaps before they become urgent.

The stale-data rules also affect how teams should read the results. By returning unknown rather than a pass when key readings exceed stated age thresholds, the software avoids presenting old measurements as proof that capacity remains available. That cautious behavior is a product rule, not evidence that the readings are always complete or current in a live environment.

Rymvard’s placement proposals and quarterly runway estimates could give hosting teams another way to compare planned deployments with site-level capacity. But the release material does not establish customer savings, improved reliability or operational outcomes. Those benefits remain possible uses of the feature set, not demonstrated results.

Read-Only SAP Data and Test Scope

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 product can also read system, customer and environment information through read-only interfaces in SAP Focused Run, ServiceNow, SAP Solution Manager via its System Landscape Directory, and SAP LaMa. Rymvard lists these as supported sources; the release does not say that customers must use all of them together.

For its reported test, Rymvard used a simulated landscape with 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, the company says the software 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. Rymvard says the screens use an illustrative estate and do not represent a real customer, site or outcome.

“Nothing is ever written to SAP.”

— Rymvard

Live Deployment Evidence Is Pending

Rymvard describes version 0.23 as early-access software and has not named a customer deployment or supplied customer results for the release. The simulated test illustrates how the checks behaved in one constructed landscape; it does not show performance across real customer environments, unusual configurations or changing workloads.

The release describes selected interfaces, query limits and data-age thresholds, but does not explain how every SAP configuration is handled or how integrations are validated in each customer environment. It also gives no broader performance data or independent evaluation. Pricing is not public; Rymvard says terms are arranged with early-access partners.

Early-Access Partner Evaluations

The next step is evaluation by early-access partners, with pricing arranged directly with Rymvard. The company has not announced a general availability date, a public price list or a named customer. Evidence from partner use would help establish how the ledger’s memory and takeover checks perform against live SAP landscapes, and whether its proposed placement and runway views fit day-to-day operations.

Until such information is published, readers should treat the release as a description of available early-access features and reported simulated testing, rather than proof of customer outcomes. Further details about supported configurations, deployment experience and how capacity readings behave in practice remain unannounced.

Key Questions

What did Rymvard add in version 0.23?

Version 0.23 adds SAP HANA host-memory accounting, placement proposals, replication takeover checks, quarterly memory runway estimates and an SAP Operations workspace.

Has Rymvard tested the release with a customer?

The supplied results are from a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. Rymvard has not identified a customer deployment or provided customer outcomes for this release.

How does the software handle old capacity readings?

Rymvard says the check returns unknown if replication status is more than one 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.” The release lists the interfaces and query limits used by the collector and monitoring connection.

When will the software be generally available, and what will it cost?

Rymvard has announced neither a broader availability date nor a public price list. It says terms are agreed directly with early-access partners.

Primary source: Rymvard · via ThorstenMeyerAI.com