SAP on OCI

SAP on OCI, certified shapes and the storage SAP needs.

OCI runs SAP and SAP HANA on certified shapes with the memory, storage, and networking SAP workloads demand. We plan the landing zone, size the systems, and migrate with the high availability SAP requires.

Engineer planning enterprise systems architecture on a whiteboard
Overview

The short version.

SAP, and SAP HANA in particular, is demanding about infrastructure. It needs certified compute shapes, large amounts of memory, fast and durable storage, and low latency between the application and database tiers. OCI supports SAP on certified configurations, and run well it gives SAP estates strong performance with a far more predictable cost than fixed hardware.

We size the SAP systems against their real load and SAP sizing guidance, design the landing zone and networking for the latency SAP needs, and migrate with high availability and disaster recovery built to SAP requirements. We are independent of both Oracle and SAP, so the design serves your estate rather than a sales target.

Why OCI

Why teams move this to OCI.

Certified shapes

OCI offers compute certified for SAP and SAP HANA, sized to memory and performance requirements.

Storage and latency SAP needs

Fast durable storage and low latency between application and database keep HANA and the SAP tiers performing.

High availability by design

We build the HA and DR SAP requires rather than bolting it on after go live.

Placement

How the options compare.

SAP tiers have strict sizing rules. We size each against SAP guidance and your real load before recommending shapes.

TierTypical placementWhy
SAP HANA databaseCertified memory rich computeMeets HANA memory and performance certification
SAP application serversRight sized compute with autoscalingCarries dialog and batch load through peaks
High availability pairAcross availability domainsKeeps the system up when a node or domain fails
SAP on OCI is a sizing and certification exercise first. Get those right and the performance follows.
Method

How we run the move.

  • Inventory the SAP landscape, products, versions, and current sizing.
  • Size each tier against SAP guidance and measured load on certified shapes.
  • Design the landing zone, networking, and HA and DR to SAP requirements.
  • Build the environment and migrate the database and application tiers.
  • Test performance and failover against real load, then cut over.
  • Hand over or run the estate under a managed monthly retainer.
40%
average OCI spend reduction after optimization
500+
OCI engagements delivered
24/7/365
managed monitoring and support
20+
years combined Oracle experience
Related

Where this connects.

Workload

Multicloud & Hybrid

Connect SAP on OCI to the rest of your cloud footprint.

See multicloud
Solution

Disaster Recovery & HA

Build SAP high availability and recovery to a stated target.

See DR and HA
Service

OCI Implementation & Migration

The team that runs the SAP move end to end.

See implementation

Plan the move before you commit.

Most teams bring in a specialist before they fix a region, a shape, or a credits number. Book an assessment and get a written plan with options and a price.