Concept card

SAP Datasphere

As of 2026-07-24T14:00:00Z

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is SAP Datasphere?

Datasphere is the governance and consumption fabric on top of HANA Cloud, not a HANA replacement — conflating the two double-counts capacity and blows the sizing budget on day one.

What is SAP Datasphere used for?

Short answer above

What it is

SAP Datasphere is the unified data and semantic layer sitting at the center of SAP's modern analytics estate. Built on SAP HANA Cloud with an integrated Delta Lake, it lets an organization model, govern, and expose enterprise data — both SAP and non-SAP — as trusted, reusable semantic objects that feed SAP Analytics Cloud, the Joule AI assistant, and third-party BI tools through open sharing protocols. In practical terms, Datasphere replaces what used to be a patchwork of point-to-point extracts, hand-built data warehouses, and brittle BEx queries with a single governed data fabric.

Why it matters

Every large SAP customer running ECC or classic BW is on a clock: SAP's roadmap steers all of them toward S/4HANA and a cloud-native analytics layer, and Datasphere is the landing zone for that migration. It is also the consumption layer beneath SAP Business Data Cloud, so getting the modeling and governance foundations right in Datasphere determines how well every downstream AI agent, dashboard, and planning application performs. A team that gets Datasphere wrong pays for it twice — once in the original project, and again in every consuming application that has to route around it.

How it works

Why it matters in practice

Pricing 'HANA Cloud' separately from Datasphere double-counts spend, since HANA Cloud is auto-provisioned from the tenant's own Capacity Unit plan.
The federate-vs-replicate call is made per source object, not per source system — defaulting to 'replicate everything' kills three architectures out of four via nightly batch windows.
There is a concrete sizing anchor to negotiate from: a 100M-row Analytic Model with daily refresh and 50 concurrent SAC users runs ~32 CU steady-state, against a 64-CU floor at roughly €52k/year.

Key points

Successor to Data Warehouse Cloud (DWC); rebranded Q1 2023; the consumption layer of BDC.
Runs on HANA Cloud + managed Delta — Datasphere is the modeling/governance fabric, not the engine.
Three pillars in one platform: federation (live push-down), replication (Replication Flows, CDC), modeling (Graphical / SQL / Script).
Three-layer modeling: raw → SQL view → Analytic Model. Always wrap raw views before exposing to SAC.
Data Access Controls (DAC) at catalog scope = one rule gates SAC + Joule + Delta Sharing + OData + JDBC.
Capacity-Unit pricing: 64 CU minimum, ~€52 k/yr FY26; CU decoupled from user seats but eaten by concurrency × dataset size.
BDC deployment shape adds Databricks lakehouse with bidirectional governance — DAC reaches Delta tables.
Performance: 100-500 ms p50 with full HANA push-down; 50-200 k rows/sec replication; 200-user concurrency cap on SAC Live.
SAP Datasphere is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.

Terms used on this page

Space: Logical delivery boundary inside a tenant — isolation for data, models and permissions. NOT a tenant; over-using as one is anti-pattern #1.
Capacity Unit (CU): Datasphere's billing unit — 1 CU ≈ 1 vCPU + 4 GB HANA Cloud + storage allotment + IOPS. Tenant minimum 64 CU.
Replication Flow: Managed pipeline that copies source tables into Datasphere on a schedule or CDC basis — 50-200 k rows/sec delta.
Analytic Model: Consumption-ready semantic object with measures, dimensions, hierarchies, calculated/restricted measures, currency conversion. The right thing to expose to SAC and Joule.
DAC (Data Access Control): Catalog-level row/column security rule — one rule reaches every consumer (SAC, Joule, Delta Share, OData, JDBC) without per-tool wiring.
Delta Sharing: Open protocol (Databricks-originated) for sharing Delta tables across organisations and tools — Datasphere supports both producer and consumer roles.
Push-down: Query execution pattern where Datasphere translates the consumer's SQL into HANA-native operations executed at the storage layer — preserves p50 100-500 ms latency.
BDC: Business Data Cloud — SAP's 2024+ flagship platform combining Datasphere semantic layer + Databricks-managed lakehouse + Joule agents under unified Unity Catalog + DAC governance.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →