SAP HANA Consulting

SAP HANA Consulting for Memory, System Replication and Recovery

SAP HANA consulting from AceMQ works at the database layer: memory and sizing review, workload and performance analysis, system replication design for high availability and disaster recovery, backup and recovery validation, revision planning and runbooks. AceMQ engineers deliver it with partner SAP HANA subject-matter experts. We do not do SAP application, Basis or ABAP work, and SAP still supports its own product. Quoted per engagement.

A senior engineer, not an SDR. No sales sequence attached.

Fastest response target, by plan
15 min
On-call cover
24/7
AceMQ customers
160+
Years in business
10+

Without handing your SAP landscape to a systems integratorFor production incident cover, see AceMQ SAP HANA 24/7 support.

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

The Problem

Why teams call us about SAP HANA

Eight SAP HANA problems an AceMQ review starts from, from memory climbing toward the allocation limit to a takeover nobody has rehearsed. If one describes your week, that is where the review starts.

  1. 01

    Memory use climbs toward the allocation limit and nobody can say which tables or workloads drive it

  2. 02

    A system replication pair exists, but nobody has run a takeover and clients have no tested way to follow it

  3. 03

    Log volume fills after the secondary site has been disconnected for days

  4. 04

    Backups run every night, but a restore of the system database and each tenant has never been rehearsed

  5. 05

    Queries slow down at month end and the column store delta has grown

  6. 06

    Savepoints take long and sessions stall when storage is slow

  7. 07

    A revision upgrade is due and the only plan is to try it on production on a weekend

  8. 08

    A move to or from SAP HANA is proposed and the database-level work has not been counted

A good fit if you run SAP HANA and want a written view of its memory, replication and recovery from engineers who work the database layer. Not a fit if you need SAP application, Basis or ABAP work, an S/4HANA project manager or SAP licensing advice.

Not a fit for small teams with non-critical workloads. AceMQ is not a budget consultancy: we work with enterprises running business-critical and compliance-heavy SAP HANA.

Running SAP HANA in production? Get a quote from a senior engineer, answered within one hour.

Contact Us

How it breaks, and the fix

What does a SAP HANA takeover need besides the takeover command?

The takeover command promotes a secondary. It does not stop the former primary, and it does not move clients. Which secondary you promote matters too: a synchronous one holds the log, an asynchronous one can be behind, and SAP says data changes may be lost during takeover.

One takeover, three sites

Applications, a client address, a primary and two secondaries

Illustrative
  1. The primary serves clients. The synchronous secondary is ACTIVE with the log persisted, and the asynchronous secondary trails by a small lag.

  2. The primary fails. The asynchronous secondary is behind, so promoting it could lose commits. Clients still point at the failed primary.

  3. The synchronous secondary is promoted with hdbnsutil -sr_takeover, the client address is moved by cluster software, DNS or a script, and the old primary stays out until it is re-registered.

A runbook covers the order: confirm the secondary is ready (REPLICATION_STATUS ACTIVE in M_SERVICE_REPLICATION), make sure the old primary is stopped or isolated, run the takeover on the secondary as the <sid>adm user, redirect clients, then re-register the old primary as a secondary with hdbnsutil -sr_register. hdbnsutil -sr_state on each site shows where the system stands. SAP's own decision guide for when to take over is SAP Note 2063657.

Our Services

SAP HANA Consulting & Support

AceMQ runs five SAP HANA service lines at the database layer: memory and sizing review, performance and workload analysis, system replication design, backup and recovery validation, and revision and migration planning. Senior AceMQ engineers lead each one, with partner SAP HANA experts.

  • 01

    Memory and Sizing Review

    A written view of where memory goes and how close the system runs to its limits, so a sizing decision rests on measurements.

    • global_allocation_limit against real use
    • Per-service memory and largest tables
    • Delta merge memory headroom
    • Growth projection and a sizing recommendation
  • 02

    Performance and Workload Analysis

    Where time goes in the database: expensive statements, merges, savepoints and storage, ranked by effect.

    • Expensive statements and their plans
    • Delta merge history and large deltas
    • Savepoint duration and storage latency
    • Workload peaks such as month end
  • 03

    System Replication, HA and DR Design

    A replication design that states its data-loss and recovery-time trade-offs, with a takeover that has been rehearsed.

    • Replication mode: SYNC, SYNCMEM or ASYNC
    • Operation mode: delta_datashipping or logreplay
    • Takeover, failback and client redirection runbook
    • Log retention and log-full protection
  • 04

    Backup and Recovery Validation

    Proof that the backups you take can be restored, for the system database and each tenant, in the time you need.

    • System and tenant database backup coverage
    • Backint or file-based backup review
    • Backup checks and a test restore on a separate system
    • Written recovery procedure and timings
  • 05

    Revision, Upgrade and Migration Planning

    A written path for the next revision, and the database-level work counted for a move, rehearsed before production.

    • Revision path and prerequisites from SAP's notes
    • Near-zero-downtime option using system replication, assessed
    • Database-level migration inventory
    • Rehearsal and rollback plan
  • Response targets from 15 minutes, by plan

    24/7 SAP HANA Support

    Senior engineers briefed on your environment, response targets from 15 minutes, by plan, and no ticket routing.

    • Response targets from 15 minutes, by plan
    • Senior engineers, no first-line triage layer
    • Proactive CVE & health monitoring
    • Quarterly deployment reviews

Want AceMQ to take this off your team's plate? Tell us about your SAP HANA estate.

Contact Us

24/7 Support

SAP HANA Support When It Matters Most

Ongoing cover for the SAP HANA database layer starts from a consulting engagement and is scoped and quoted per estate, with a senior AceMQ engineer assigned to your account. SAP supports SAP HANA itself and ships its fixes; AceMQ does not.

  1. From 15 min (by plan)first responseEmergencyProduction down, messages not flowing, queue manager failure
  2. 1 hourfirst responseCriticalSevere degradation, high error rates, approaching capacity
  3. 4 hoursfirst responseHighPerformance issues, configuration problems, non-critical failures
  4. Next Dayfirst responseStandardQuestions, guidance, best practices, non-urgent improvements

Response targets by plan; your contract sets the tier.

P1 escalation path

A replay of one P1, from the first page to the written root-cause analysis

SLA 15:00
T+Elapsed15:00
Engineer on your bridge

Response targets from 15 minutes, by plan; 24/7.
A response time, not a resolution time.

  1. T+00:00

    P1 opened, on-call engineer paged

    Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in RabbitMQ, Kafka, Redis, PostgreSQL or Kubernetes. No web form, no tier-1 queue.

    Paged
  2. T+15:00

    Senior engineer on your bridge

    A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.

    Live
  3. T+30:00

    Specialists across the stack join

    When an incident crosses components, the engineers who know each one join. For RabbitMQ, the path runs to the core team.

    If needed
  4. After

    Written root-cause analysis

    Root cause, the fix applied and the prevention steps, delivered after every P1.

    Every P1

How Our Support Actually Works

Beyond SLAs — the model behind senior-only, zero-cold-start expert access.

  • Engineers Who Know Your Environment

    Tickets go to senior engineers briefed on your environment, not an anonymous queue. The proposal states who does the work.

  • Live Escalation on Any Ticket

    Any ticket can be escalated to a live session with an engineer through calendar booking. No gatekeeping and no approval step.

  • Proactive Risk Mitigation

    Scheduled health checks on your deployment and alerts on risks in the versions you run, so problems surface before they reach production.

  • Critical Bug & CVE Intelligence

    Proactive alerts on critical bugs and CVEs affecting your exact version, with version compliance monitoring so you're never caught off guard.

How It Works

What actually happens next

An AceMQ SAP HANA engagement runs in four stages: a scoping call with a quote within 1 hour, a read-only review, a written plan, then the work or a handover. Each stage ends in writing.

Quote within 1 hour

Scoping call and quote

A senior AceMQ engineer asks what you run: the HANA 2.0 revision, scale-up or scale-out, whether system replication exists and in which modes, the backup tool, and what has prompted the question. We say plainly whether the work sits at the database layer, where we are useful, or in the SAP application layer, where we are not. A quote request is answered within 1 hour.

Scoped per estate

Read-only review

The configuration and state read with your DBAs: memory against the allocation limit, table and delta sizes, savepoint and merge behavior, replication state and modes, backup catalog and restore tests, and the monitoring that exists. Findings are written down and your team keeps them.

Scoped per estate

Written plan

A recommendation in writing: sizing and configuration changes, the replication design and its takeover procedure, the backup and recovery test plan, and the revision path. Anything that needs SAP's answer is marked as a question for SAP, not guessed.

Ongoing or fixed scope

Run the work or hand over

Changes staged on a copy first, then production one step at a time with a rollback for each. The work ends with runbooks for takeover, failback, backup restore and the next revision. You can stop there, or ask about ongoing cover for the database layer.

  • Written findings before any change
  • Changes staged and reversible, with a rollback plan
  • Your DBAs in the room
  • Ad hoc engagements or an annual partnership

A senior engineer, not an SDR. No sales sequence attached.

Typical engagements

How SAP HANA engagements run

Typical SAP HANA engagements from AceMQ: what the environment looks like, what AceMQ assesses or designs, and what the engagement delivers.

  • Assessment

    SAP HANA Memory and Workload Review

    Database Operations Team

    A typical engagement for a team whose SAP HANA system runs close to its memory limit: where memory goes, which tables and merges drive it, what the savepoint and storage numbers say, and a written sizing recommendation.

    SAP HANASAP HANA cockpit
  • Consulting

    SAP HANA System Replication and HA Design

    Infrastructure Team

    A typical engagement to design SAP HANA system replication for high availability and disaster recovery: replication and operation modes chosen against the data-loss and recovery-time targets, and a takeover, failback and client-redirection runbook that has been rehearsed.

    SAP HANASAP HANA system replicationhdbnsutil
  • From our database practice

    Grafana Outage and Datasource Timeout Remediation

    Telecommunications Operator

    Remediation of a Grafana deployment that became unusable during incidents, with dashboards timing out exactly when engineers needed them most.

    GrafanaPrometheusKubernetesPostgreSQL
All use cases

Solutions

Every way AceMQ works with SAP HANA.

AceMQ covers SAP HANA end to end. Projects: consulting and implementation, health checks and migrations. Ongoing cover in four tiers, from 24/7 support and incident management to proactive monitoring, managed SAP HANA on your infrastructure and fully managed SAP HANA on AceMQ infrastructure, plus end-of-life versions.

Projects

Build, fix or move SAP HANA

Fixed-scope work led by a senior engineer: architecture and new builds, a health check of what you run today, or a migration with a reversible cutover.

Side by side

SAP, your SAP partner or AceMQ: who does what on a SAP HANA estate?

SAP supports SAP HANA, ships its revisions and holds the licence. AceMQ adds engineers who work the database layer with partner SAP HANA experts. AceMQ is not an SAP partner and does not replace SAP. Each row answers one question about the split.

SAP and AceMQ compared on product support, fixes, database-layer design, application work, licensing and how each is bought
QuestionSAP, under your SAP agreementAceMQ database-layer consulting
Who supports the SAP HANA product?SAP, under the terms of your agreement.SAP stays the product vendor. AceMQ does not replace SAP support and tells you when a question is for SAP.
Who supplies revisions and fixes?SAP ships SAP HANA revisions and fixes.AceMQ produces no SAP patches. We plan the revision path and rehearse it.
Who designs memory, replication and backups?SAP documents the options in its guides and notes.The core of our work: sizing review, replication mode and takeover design, restore testing.
Who does SAP application, Basis and ABAP work?SAP and its partners.Not AceMQ. We do no SAP application, Basis or functional consulting, no ABAP development and no S/4HANA project management.
Who advises on SAP licensing?SAP holds the licence and its terms.Not AceMQ. We give no SAP licensing advice.
How is it bought?Through your SAP agreement.Quoted per engagement. Quote requests are answered within 1 hour.

AceMQ is independent of SAP. Read your SAP agreement and SAP's maintenance information for your release before you plan.

Not sure which option fits? A senior SAP HANA engineer will scope it with you.

Contact Us

One partner, not five

We Support Your Entire Tech Stack

SAP HANA rarely fails in isolation. AceMQ covers the full surrounding infrastructure — so one team owns the whole path instead of pointing at each other.

See all the technologies we supportShow fewer

Scope

What AceMQ does and does not do on a SAP HANA estate

AceMQ engineers work at the SAP HANA database layer, with partner SAP HANA subject-matter experts. Anything above the database belongs to your SAP team or your SAP partner, and SAP supports its own product.

What AceMQ does and does not do on a SAP HANA estate, by area of work
AreaAceMQ doesAceMQ does not do
Memory and sizingReads memory use against global_allocation_limit, per-service use and the largest tables, and writes a sizing recommendationReplace SAP's own sizing guidance for an SAP application
PerformanceAnalyzes expensive statements, delta merges, savepoints and storage latency at the databaseTune ABAP code or SAP application logic
High availability and disaster recoveryDesigns system replication, writes the takeover and failback runbook, reviews log retentionBuild the SAP application tier failover or run the SAP Basis team
Backup and recoveryReviews system and tenant backups, runs backup checks and a test restore, times the procedureSell or support the backup product behind Backint
Revisions and upgradesPlans the revision path from SAP's notes, assesses a near-zero-downtime upgrade with system replication, rehearses itProvide SAP patches or fixes: SAP ships them under your SAP agreement
MigrationCounts the database-level work in a move and rehearses the cutoverManage an S/4HANA implementation project or do functional consulting
Licensing and supportTells you plainly when a question is for SAPGive SAP licensing advice, or replace SAP support, or claim to be an SAP partner

Pricing is quoted per engagement, after the scoping call, with a reply to quote requests within 1 hour. For other databases, see database consulting and database support. If you also run SAP ASE, see SAP ASE (Sybase) DBA services.

What we check first

SAP HANA problems teams bring to AceMQ, and what we check first

Each row starts from what you see. The views, commands and parameters are SAP's own, checked against SAP's documentation on help.sap.com on 19 November 2026.

SAP HANA symptoms and what AceMQ checks first
What you seeWhat we check first
Memory use climbs toward the limitglobal_allocation_limit in the memorymanager section of global.ini against ALLOCATION_LIMIT and use in M_HOST_RESOURCE_UTILIZATION and M_SERVICE_MEMORY, then memory by component and by table in the SAP HANA cockpit memory analysis
A table is slow and its delta keeps growingThe delta size in M_CS_TABLES and the merge history in M_DELTA_MERGE_STATISTICS, and whether there is memory headroom for the merge to run
Stalls that line up with savepointsSavepoint duration against the default 5-minute interval and storage latency on the data volume, since SAP notes poor I/O can stretch the savepoint's critical phase
The log volume is filling and the secondary is goneRetainedFree log segments from a disconnected secondary, logshipping_max_retention_size, and whether the old secondary was unregistered (sr_unregister) or disabled (sr_disable)
Writes stop when the network to the secondary dropsWhether SYNC runs with the full sync option, [system_replication]/enable_full_sync, which suspends primary writes while the secondary is disconnected
Nobody is sure the replication pair is healthyhdbnsutil -sr_state on each site, REPLICATION_STATUS in M_SERVICE_REPLICATION, and the replication and operation modes actually registered
A takeover was run and the application still points at the old hostHow clients are redirected: virtual IP, DNS, cluster management software or an HA/DR provider script, and whether the former primary was stopped or isolated
A restore has never been triedBackup catalog and Backint configuration for the system database and each tenant, hdbbackupdiag and hdbbackupcheck results, and a test restore with a timed procedure

Design choices

SAP HANA system replication modes: what each choice costs and gives

Two settings decide most of a replication design: when the primary commits, and what the secondary does with the data it receives. Both are set when the secondary is registered with hdbnsutil -sr_register (SAP HANA System Replication Guide, SPS 08, read 19 November 2026).

SAP HANA system replication replication modes and operation modes with what each costs and gives
SettingWhat it doesWhat it costs or risks
SYNCThe primary commits after the log is persisted on the secondaryEach commit waits for the secondary's disk. Data loss is possible if a takeover runs while the secondary is disconnected
SYNCMEMThe primary commits after the secondary has the log in memoryShorter delay than SYNC, but data can be lost if both systems fail at the same time
ASYNCThe primary commits without waiting for a replyNo commit delay. SAP states data changes may be lost during takeover
delta_datashippingContinuous log shipping plus a delta data shipping, by default every 10 minutesThe secondary does not replay the log until it takes over, so takeover takes longer
logreplayOne full data shipping, then the redo log is replayed on the secondary as it arrivesTakeover is immediate, but the primary retains log for a disconnected secondary up to logshipping_max_retention_size, and a full data snapshot follows if that limit is reached
logreplay_readaccessAs logreplay, and the secondary can be read (Active/Active, read enabled)The same continuous log shipping and replay as logreplay. Read access on the secondary is the reason to choose it

Multitarget system replication, where one primary feeds more than one secondary, supports only logreplay and logreplay_readaccess, and logreplay cannot be combined with delta_datashipping across tiers or targets. SAP's maintenance dates for a HANA revision are in SAP's own revision and maintenance note, which needs a SAP login, so AceMQ works from the date in your copy and prints none here.

FAQs

SAP HANA Questions Answered

Answers on SAP HANA consulting from AceMQ: what is and is not covered, why memory runs high, how to choose a replication mode, whether failover is automatic and how a backup restore is tested.

Still have questions about SAP HANA? Email an Expert

What does SAP HANA consulting from AceMQ cover, and what does it not?

AceMQ covers the database layer: memory and sizing review, performance and workload analysis, system replication design, backup and recovery validation, revision planning, runbooks and database-level migration planning, delivered by AceMQ engineers with partner SAP HANA subject-matter experts. AceMQ does not do SAP application, Basis or functional consulting, ABAP development, S/4HANA implementation project management or SAP licensing advice. SAP supports its own product and holds the licence, and AceMQ is not an SAP partner.

Why is SAP HANA using so much memory, and is that normal?

HANA is an in-memory database that keeps data in memory and takes the memory it needs up to a limit. That limit is global_allocation_limit, set in the memorymanager section of global.ini in MB; when it is not set, SAP documents a default derived from physical memory. The useful question is what sits under that limit. M_HOST_RESOURCE_UTILIZATION and M_SERVICE_MEMORY show the limit and the use, and the memory analysis in SAP HANA cockpit breaks use down by component and table. Column-store tables also need headroom for delta merges, because SAP says a merge needs roughly the current main, the new main and the delta in memory at once (help.sap.com, read 19 November 2026).

How do I choose between SYNC, SYNCMEM and ASYNC system replication?

It is a trade between commit delay and data loss. In SYNC the primary waits until the log is persisted on the secondary. In SYNCMEM it waits only until the secondary has the log in memory, so it is faster but data can be lost if both systems fail together. In ASYNC the primary does not wait, and SAP says data changes may be lost during takeover (SAP HANA System Replication Guide, SPS 08, read 19 November 2026). Distance and latency to the secondary decide what you can afford, so we measure them before recommending.

Does SAP HANA fail over automatically?

SAP HANA provides the takeover, run with hdbnsutil -sr_takeover on the secondary. SAP's guide describes moving clients by IP redirection, DNS or cluster management software, and HA/DR provider scripts that can run actions after a takeover. Whether your estate has automatic failover depends on what has been built around the replication pair, so we check that, and test it, rather than assume it.

How do you test that a SAP HANA backup can really be restored?

By restoring it on a separate system, which SAP recommends before relying on a recovery. SAP provides hdbbackupdiag to check that the files a recovery needs are present, hdbbackupcheck to check a backup for corruption, and a CHECK ACCESS option on RECOVER DATABASE that confirms the backups are reachable before a recovery starts. The system database and each tenant database are recovered separately, and we time the whole procedure.

Can we work with AceMQ on SAP HANA without a long contract?

Yes. AceMQ works on SAP HANA in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual contract that covers 24/7 support and proactive reviews. Many teams start ad hoc and move to an annual contract once the first engagement is done.

How much does AceMQ SAP HANA support or consulting cost?

Every AceMQ proposal is tailored to your requirements: your SAP HANA environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how SAP HANA is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.

Let's talk

Find Out How Close Your SAP HANA System Runs to Its Limits

Send us your HANA revision, scale-up or scale-out layout, replication setup and what has prompted the question. We reply to quote requests within 1 hour.

A senior AceMQ engineer, not a sales queueAbout your SAP HANA estate, not a pitch deckQuote requests answered within 1 hour

Production incident right now?Email a SAP HANA Architect

Get in Touch

Talk to a SAP HANA Expert

Send us a message and we'll follow up within 1 hour — or book a free 30-min consultation directly.

305-204-2607
info@acemq.com
66 W. Flagler St. 9th Floor
Miami, FL 33130

Prefer to talk now? Call us directly or use the consultation tab to find a time that works.

We respond within 1 hour.

Pick a time that works — no pressure, no pitch. Just 30 minutes with an expert.

We respond within 1 hour.