Rymvard Integrates SAP HANA Memory Into Data Center Capacity Records

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

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

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 company tested the early-access software on a simulated landscape, not a customer deployment, so real-world performance and customer outcomes remain unreported.

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 software is aimed at SAP hosting providers and operations teams, but Rymvard’s reported tests used a simulated estate, not a customer deployment.

The release breaks down each HANA host’s physical memory into an operating-system reserve, memory used by HANA systems, allocated but unused memory, capacity reserved for replicas from other sites, and remaining free memory. Unless a host has a different setting, the reserve is 10% of the first 64 GiB and 3% of memory beyond that. System usage is calculated from its 30-day peak. If allocations exceed physical memory, the ledger labels the host overbooked rather than displaying a negative free-memory figure.

For systems using SAP HANA system replication, the software checks whether a secondary host could handle the primary system’s allocation after takeover. It reports whether the allocation fits, fits after named test or development systems are stopped, falls short by a specified number of 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 memory data older than 24 hours produces an unknown result, rather than 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 probability. Rymvard says HANA instances are mirrored into its compute view for customer showback and lifecycle planning. Its new SAP Operations workspace displays free HANA memory, production systems without replication, takeovers that would fail, and hosts above 90% utilization.

Making HANA Failover Capacity Visible

The release addresses a specific planning problem for providers: a data center can have capacity across its wider infrastructure while an individual HANA host or replication partner lacks the memory needed for a system. By distinguishing free, allocated, reserved and overbooked memory, the ledger is designed to surface constraints that broader facility-capacity figures can miss.

The takeover checks could help operations teams identify a replication shortfall before a failover is needed, while placement proposals and quarterly runway estimates may help compare planned deployments with capacity at each site. These are intended uses, not demonstrated outcomes. The supplied information does not establish cost savings, improved reliability or customer results; those would depend on accurate source data and how the product performs in live environments.

Rymvard’s stale-data rules also affect how teams should interpret the checks. Marking an outdated reading as unknown avoids treating old measurements as proof of available capacity. At the same time, users would need current and dependable monitoring data to get a useful assessment. For providers evaluating the product, the distinction between documented functionality and proven performance matters: the release describes the former, while real-world evidence has not been supplied.

Read-Only SAP Data Connections

Rymvard says its collector connects to the SAP Host Agent over HTTPS and uses four permitted 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. Rymvard lists these as supported sources; the release material does not say that customers must connect all of them.

Rymvard reports testing version 0.23 against a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, it identified 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. The company says the displayed screens use an illustrative estate, not a customer environment, and that the examples do not represent a real customer, site or outcome.

“Nothing is ever written to SAP.”

— Rymvard

Live Customer Results Remain Unreported

Rymvard describes version 0.23 as early-access software and has not identified a customer deployment or supplied customer outcomes. The reported test results come from a simulated landscape, so they do not show how the software performs across live customer environments, unusual SAP configurations or workloads that change over time.

The release describes its data-age thresholds and connection limits, but does not provide independent evaluations or further detail on how integrations are validated in each environment. Rymvard has not published prices, saying terms are arranged with early-access partners. A broader availability date and a named customer have not been announced.

Early-Access Partner Evaluations

The next stated step is evaluation by early-access partners, with commercial terms arranged directly with Rymvard. The company has not announced a public price list or a date for broader availability.

Further evidence to watch for includes named customer deployments, results from live environments, and details on how the capacity checks perform across different SAP landscapes. Until Rymvard provides those, the release establishes the product’s described capabilities and simulated test findings, but not its operational outcomes for customers.

Key Questions

What did Rymvard add in version 0.23?

It added SAP HANA host-memory accounting, system placement proposals, replication takeover-capacity checks, and a workspace with operational indicators for HANA capacity.

Did Rymvard test the release at a customer site?

No customer deployment is reported. Rymvard says its test used a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs.

How does the software report a takeover shortfall?

It reports whether a secondary host can accommodate the primary system, whether named test or development systems must be stopped, or the size of a memory shortfall. If replication data is over one hour old or memory data over 24 hours old, the result is unknown.

Does Rymvard write data to SAP?

Rymvard says its SAP connections are read-only and states, “Nothing is ever written to SAP.” It describes read operations through the SAP Host Agent and other supported landscape sources.

When will the software be generally available?

Rymvard has not announced a broader availability date. The immediate next step is evaluation by early-access partners, with pricing arranged directly with the company.

Primary source: Rymvard · via ThorstenMeyerAI.com