AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: Can Hosting Providers Track SAP HANA Memory In The Capacity Ledger? on Rymvard

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

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
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

Can Hosting Providers Track SAP HANA Memory In The Capacity Ledger?

Rymvard released version 0.23 on Oct. 4, 2026, adding SAP and HANA hosting support to its data-center capacity ledger. The early-access software tracks HANA memory use and replication capacity, but its published test results come from a simulated estate, not a customer deployment.

Rymvard released version 0.23 on Oct. 4, 2026, adding SAP and HANA hosting support to its data-center capacity ledger. The early-access release is aimed at SAP hosting providers and operations teams, with tools to account for HANA memory, check whether replication partners can take over workloads, and plan capacity for upcoming systems.

The ledger breaks each HANA host’s physical memory into an operating-system reserve, memory used by HANA systems, allocated but unused memory, memory reserved for replicas at other sites, and free memory. By default, the reserve is 10% of the first 64 GiB and 3% of the remainder, unless a host specifies its own reserve. HANA system use is based on its 30-day peak. Allocations above physical capacity appear as overbooking rather than being concealed as negative free memory.

For each HANA system using system replication, Rymvard checks whether the secondary host can carry the primary system’s allocation after a takeover. The check can account for stopping test and development systems on the secondary, but it does not treat another customer’s production systems as stoppable. Results are reported as a fit, a fit after named systems are stopped, a failure with a shortfall in GiB, or unknown. If replication status is more than one hour old, or a memory reading is more than 24 hours old, the result is marked unknown. For scale-out systems, the overall assessment uses the weakest host pair.

The release also proposes a host and replication-site partner when placing a new HANA system, and converts planned go-lives, weighted by their probability, into a memory runway by site and quarter. HANA instances are mirrored into Rymvard’s compute view, allowing SAP memory to appear in customer showback and lifecycle planning. A new SAP Operations workspace highlights free HANA memory, production systems without replication, takeovers that would fail, and HANA hosts above 90% capacity.

At a glance
announcementWhen: Released Oct. 4, 2026; early access
The developmentRymvard version 0.23 adds SAP HANA memory accounting and replication capacity checks to its data-center capacity ledger.
Can Hosting Providers Track SAP HANA Memory In The Capacity Ledger?

Capacity Ledger · Early Access · Oct. 4, 2026

Can Hosting Providers Track SAP HANA Memory In The Capacity Ledger?

Rymvard version 0.23 adds HANA memory accounting, replication takeover checks and capacity planning for SAP hosting teams. Published results come from a simulated estate, with customer performance still unreported.

Release focus Memory + recovery

See allocated capacity, replica reserves and takeover fit across sites.

Evidence status Simulation only

Illustrative screens and simulated findings; no customer deployment results reported.

Version0.23SAP HANA hosting support
Simulated hosts200Across the example landscape
HANA systems161Included in reported simulation
Replicated pairs39Takeover checks exercised
01 / Memory accounting

One host, five memory buckets

The ledger separates what is in use from what is committed, reserved for recovery or still available.

Illustrative host memory breakdown

Conceptual allocation view — not a reported customer host measurement.

Operating-system reserve
HANA system use
Allocated, unused
Replica reserve
Free memory
Default reserve

10% of the first 64 GiB, then 3% of the remaining memory, unless the host defines its own reserve.

Observed use

HANA system use is based on its 30-day peak to represent recent high-water demand.

Overbooking

Allocations above physical capacity are shown as overbooking instead of hidden as negative free memory.

02 / Replication takeover

Can the secondary carry the primary?

Each replication check compares the primary allocation with capacity at the secondary host after takeover.

✓ Fit

The secondary has capacity to carry the primary system allocation.

~ Fit after stop

A fit is possible after named test or development systems on the secondary are stopped.

✗ Shortfall

The takeover does not fit; the result includes the capacity gap in GiB.

? Unknown

Evidence is stale, so the system cannot confirm a safe fit.

03 / Planning workflow

From live estate to planned runway

Version 0.23 connects current HANA capacity to placement proposals and probability-weighted demand.

1Account

Mirror HANA instances into the compute view for showback and lifecycle planning.

2Check

Assess host memory and whether replication partners can carry a takeover.

3Place

Propose a host and replication-site partner for a new HANA system.

4Forecast

Convert likely go-lives into a memory runway by site and quarter.

Capacity view

Free HANA memory

Operations

Unreplicated production and failing takeovers

Threshold

Hosts above 90% capacity

Planning

Demand runway for upcoming systems

04 / Capacity runway

Plan demand across sites and quarters

Planned go-lives are weighted by probability and compared with available memory. The bars below are illustrative only.

Site A
72%
Site B
48%
Site C
88%
Site D
31%
Planning signal

Probability-weighted go-lives

Compare expected incoming memory demand with site capacity over time. Usefulness depends on complete, fresh ledger data and realistic probability estimates.

05 / What the evidence shows

Simulated findings, not customer outcomes

Rymvard’s simulated landscape

1Production system without replication
512 GiBTakeover shortfall detected
128 GiBHost overbooked
1Replication in error state

The company says screens show a running product on an illustrative estate, not a customer environment. These results have not been independently validated in the release information.

“A replication status older than one hour or a memory figure older than 24 hours makes the result unknown — never fine.”
Rymvard · Product description
“Nothing is ever written to SAP.”
Rymvard · Read-only connection claim
06 / SAP connections

Read-only access by design

Rymvard describes bounded reads from SAP and landscape tools. The approach does not by itself establish performance across customer environments.

A site-level collector communicates with SAP Host Agent over HTTPS. A separate connection reads HANA monitoring views using fixed queries, TLS and limits on query time and concurrency.

Host Agent

Four accepted reads: ListInstances, ListDatabases, GetDatabaseStatus and GetComputerSystem. Other operations are rejected.

HANA views

Six fixed SELECT queries; 60-second limit per system and up to eight systems queried at once.

Landscape sources

Read-only interfaces in SAP Focused Run, ServiceNow, SAP Solution Manager SLD and SAP LaMa.

Product claim

Rymvard says its software does not write to SAP.

Validation still needed: Live performance, data quality and integration behavior across different customer landscapes have not been reported.
07 / Early-access outlook

What providers should watch next

Version 0.23 is in early access. Pricing is agreed with early-access partners; no general-availability date or broader release schedule is stated.

Capabilities described

  • HANA memory accounting and visible overbooking
  • Replication takeover fit and stale-data status
  • System placement proposals and quarterly runway planning
  • SAP memory in customer showback and lifecycle planning

Evidence still open

  • Customer deployment results and live-estate performance
  • Number of early-access partners
  • Independent validation of the simulated findings
  • General-availability timing and published pricing

HANA Memory and Takeover Risk

For providers running SAP infrastructure, memory can become the binding capacity constraint before power does, according to Rymvard’s description of the product’s target use case. Tracking only current consumption may miss memory already allocated to systems, capacity reserved for replication, or the room needed to recover workloads after a site or host failure.

The release brings those factors into a shared capacity view. A takeover result marked unknown rather than safe when monitoring data is stale can help operators distinguish a verified fit from a lack of current evidence. Showing overbooking directly may also make it easier to spot commitments that exceed physical memory before adding more systems. These are product capabilities; Rymvard has not published evidence here of operational outcomes at a customer site.

Planning placements and probable go-lives against a quarterly memory runway could help hosting teams compare incoming demand with available capacity across sites. Its usefulness will depend on the freshness and completeness of the data connected to the ledger, as well as the accuracy of planned go-live probabilities.

Amazon

SAP HANA memory monitoring tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Read-Only SAP Data Connections

Rymvard says the product connects to SAP in read-only mode. A site-level collector communicates with SAP Host Agent over HTTPS and accepts four read operations: ListInstances, ListDatabases, GetDatabaseStatus and GetComputerSystem. It rejects other operations. A separate connection queries HANA monitoring views using six fixed SELECT queries, with TLS, a 60-second limit per system and a maximum of eight systems queried at once.

Landscape information can also come from read-only interfaces in SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa. Rymvard says the software does not write to SAP. The stated access limits and read-only design describe the product’s approach; they do not independently establish how it will perform across different customer environments.

Rymvard reports testing the release against a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. In that simulation, it identified one production system without replication, one takeover that would not fit with a 512 GiB shortfall, one host overbooked by 128 GiB, and one replication in an error state. The company says the product is in early access and that displayed screens use an illustrative estate, not a customer environment.

“Nothing is ever written to SAP.”

— Rymvard

Amazon

data center capacity planning software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Customer Performance Remains Unreported

Rymvard has not reported results from a customer deployment. Its published counts and detected capacity issues are from a simulated SAP landscape, and the company says the screens shown are based on an illustrative estate. It is not clear how the system performs across live customer environments, including estates with different configurations, data quality or monitoring practices.

The company has also not published pricing; it says terms are agreed with early-access partners. The release description does not specify how many partners are participating, when general availability might begin, or whether the simulation’s findings have been independently validated. Those points remain open.

Amazon

HANA replication capacity check software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Early-Access Rollout and Validation

Rymvard says version 0.23 is available in early access, with pricing handled through agreements with early-access partners. The next evidence to watch for is whether the company reports customer deployments, live-estate results or changes to the product’s SAP integrations and capacity checks. No general-availability date or broader release schedule has been announced in the information available.

Hosting providers considering the release would need to evaluate its connections and reporting against their own SAP landscapes, including the freshness of replication and memory data used for takeover judgments. Rymvard lists contact@rymvard.com for inquiries. The company has not disclosed a timeline for moving beyond early access.

Source: Rymvard

Amazon

server memory capacity ledger

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?

Version 0.23 adds SAP and HANA hosting support to Rymvard’s capacity ledger, including HANA memory accounting, replication takeover checks, system placement proposals and memory runway planning.

Does the software write data to SAP?

Rymvard says its SAP connections are read-only and that nothing is written to SAP. The stated integrations use four read operations through SAP Host Agent, fixed SELECT queries against HANA monitoring views, and read-only interfaces in landscape tools.

How does Rymvard assess HANA replication takeovers?

It checks whether a secondary host can carry the primary system’s allocation. The result can be a fit, a fit after named test or development systems are stopped, a failure with a shortfall, or unknown when relevant status or memory data is stale.

Has Rymvard reported customer test results?

No customer results are reported in the release information. Rymvard describes testing on a simulated estate of 200 HANA hosts, 161 systems and 39 replicated pairs, and says its displayed screens use an illustrative example rather than a customer environment.

Is Rymvard version 0.23 generally available?

The release is in early access. Rymvard has not announced a general-availability date, and says pricing is agreed with early-access partners.

Source: Rymvard

HALLOWEEN

Halloween Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

Email Platform Migration? Automate Your Flow Rebuilding Process

A new automation-flow rebuild tool targets agencies, streamlining email migration by translating automation logic across platforms, reducing manual effort.

DaVinci Resolve 21.1

Blackmagic Design releases DaVinci Resolve 21.1, introducing new features and improvements for video editing and color grading, with details still emerging.

The Delegation Ladder: The Four Agentic Loops, And What Each One Lets You Stop Doing

Exploring the four levels of agentic loops in AI engineering, what each allows you to stop doing, and their implications for automation and control.

The Future Of Flipper Zero Development

Developers reveal plans for ongoing updates and new features for Flipper Zero, emphasizing community engagement and security improvements.