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.