SAP Datasphere vs SAP Business Data Cloud
Business Data Cloud brings Datasphere, Analytics Cloud, HANA Cloud, and lifted SAP BW systems together as one capacity-licensed platform with zero-copy ecosystem access. Understand the architectural relationship, licensing shift, and when this matters for your strategy.
The relationship at a glance
SAP Business Data Cloud is not a replacement for Datasphere—it is a commercial and strategic superset. BDC unifies SAP's data foundation — SAP Datasphere for semantic modeling, SAP Analytics Cloud for analytics and planning, and SAP HANA Cloud as the underlying AI database — together with SAP Master Data Governance and SAP Reltio (generally available inside BDC since October 2026) for master data, while existing SAP BW and BW/4HANA systems can be lifted in as private cloud editions and expose their data as data products through the Data Product Generator. It adds a unifying capacity-based licensing model and zero-copy data sharing to external platforms via BDC Connect.
Key takeaway
Datasphere remains the semantic core within BDC. The shift from standalone licensing to bundled BDC + capacity units is commercial, not architectural. Your semantic modeling work doesn't change; the packaging and partner integration strategy evolves.
What's actually bundled in Business Data Cloud
SAP Datasphere (semantic core)
- Semantic modeling with analytic models and business-layer definitions of measures, dimensions and hierarchies
- Data integration with replication flows, transformation flows and task chains — Oracle and Snowflake were added as replication sources (initial load) during 2026
- Federation to remote sources without copying data
- Custom data products on the BDC object store, including BW data exposed through the Data Product Generator
- Catalog with data product governance: terms of use, steward approval and access agreements since September 2026
Role in BDC: Foundation layer where trusted business meaning lives, shared by SAC and BI tools across the platform. Data Product Studio, announced to streamline packaging this governed data as data products, had no confirmed general availability when this page was reviewed in November 2026.
SAP Analytics Cloud (moved to capacity units)
- Planning and budgeting, including seamless planning, which stores SAC planning-model data directly in SAP Datasphere
- Business intelligence with stories, dashboards and analytic applications in the Optimized Story Experience
- Predictive scenarios for classification, regression and time-series forecasting
- Agentic BDC capabilities for SAC — AI-generated stories, natural-language insights, generated planning and analytical models — announced at SAP Sapphire 2026 in private preview
- Licensed through BDC capacity units for new customers
Role in BDC: Enterprise analytics and planning layer, typically consuming Datasphere's semantic models alongside live connections to SAP sources where they make sense.
SAP BW and BW/4HANA (private cloud edition)
- Existing SAP BW 7.5 and BW/4HANA systems lifted into BDC as private cloud editions
- Maintenance: SAP BW on NetWeaver to the end of 2030, SAP BW/4HANA to 2040
- InfoProvider models, process chains and reporting keep running during modernization
- The Data Product Generator exposes BW data as custom data products for Datasphere and SAP Databricks, or for external Databricks through BDC Connect
- Runs as a BDC capacity service (listed by SAP as SAP Business Warehouse Cloud)
Role in BDC: Coexistence layer that protects existing BW investments while data moves into data products and Datasphere models.
BDC Connect (zero-copy sharing)
- Databricks: GA October 2025
- Snowflake: GA May 4, 2026
- Google BigQuery: GA July 2026
- Microsoft Fabric: public preview (GA not yet announced)
- Amazon Athena: planned for H1 2027
- Partners query shared data products in place, without ETL, and can publish data products back
Role in BDC: Shares SAP-managed and custom data products with external platforms without copying, with business semantics carried in each product's metadata. Architects can use best-of-breed tools while governance of what is shared stays in BDC.
SAP Databricks note
SAP Databricks — Databricks delivered inside BDC as an SAP capacity service — has been generally available since April 2025, making Databricks-based lakehouses a first-class option within BDC rather than a separate platform choice. SAP Snowflake has offered the same model for Snowflake since May 2026, and at SAP TechEd 2026 the Databricks partnership was extended with Lakeflow, Agent Bricks, Unity Gateway, and Lakebase for SAP Databricks plus a Joule–Genie integration.
Licensing and commercial implications
BDC Core Capacity Units (unified model)
Business Data Cloud uses a capacity-unit licensing model. You subscribe to BDC core capacity and apply the capacity units across its services:
- SAP Datasphere and SAP Analytics Cloud
- SAP HANA Cloud and SAP S/4HANA Cloud for master data governance (extra stack)
- SAP Business Warehouse Cloud for lifted BW systems
- SAP Databricks and BDC Connect
Each service consumes capacity units at its own rate, and intelligent packages with curated data products are purchased separately. Size with SAP's capacity unit estimator rather than per-seat assumptions.
SAC licensing transition (key change)
On January 1, 2026, SAP removed SAP Analytics Cloud from the cloud services eligible for new BTPEA, CPEA and pay-as-you-go subscriptions, and it can no longer be renewed under those agreements. SAP's pricing pages now route new SAC licensing through BDC core capacity. Existing agreements, including cloud credits bought before January 1, 2026, can be used until their term ends, and existing tenants move to BDC without technical migration.
This is a commercial packaging change, not a functional change. SAC capability remains the same; licensing becomes aligned with the broader BDC platform.
Datasphere bundling (no separate purchase)
The same change applies to SAP Datasphere: since January 1, 2026 it is no longer available for new BTPEA, CPEA or pay-as-you-go subscriptions or renewals, and new Datasphere licensing goes through Business Data Cloud.
SAP calls moving an existing tenant to BDC “rewiring”: the commercial model and lifecycle management (through SAP for Me) change, while the tenant itself and its content stay the same.
BDC Connect capacity (sharing costs)
BDC Connect is itself a BDC capacity service. SAP meters it on inter-region data transfer (per GB) and processing requests (per block of API calls), so sharing within one region keeps the transfer charge out of the picture.
Queries against shared data products run on the partner platform and are billed there — Databricks compute, Snowflake credits or BigQuery capacity — so budget both sides.
Data products: where things stand in November 2026
Data products are how BDC packages governed data for reuse. SAP-managed data products are curated by SAP from its applications; custom data products are built in Datasphere, including from BW through the Data Product Generator. Data Product Studio — announced at SAP TechEd 2025 as the workspace for defining, versioning, and publishing data products, with general availability planned for H1 2026 — had no confirmed GA when this page was reviewed. Meanwhile, BDC's September 2026 release added data product governance, and SAP Reltio, generally available inside BDC since October 2026, brings AI-based entity resolution and data quality to master data. Together, these move data governance from metadata toward active, business-informed data quality.
What a data product is
A bundled unit combining:
- Curated data (SAP-managed, or custom-built in Datasphere)
- Metadata described with SAP's open standards (ORD and CSN)
- Semantic definitions (metrics, dimensions, KPIs)
- Access controls and governance policies
- Consumption through SAP services or BDC Connect partners
Think of it as a packaged, reusable, governed data offering—not raw tables, but business-meaning-wrapped data.
Why this matters architecturally
Data Products standardize how governed data moves across your organization and ecosystem. Instead of ad-hoc exports and API calls, teams publish and subscribe to versioned, documented, semantically consistent products. Datasphere models the core; the BDC catalog publishes, governs, and shares the output.
What is available now
Today you can create custom data products in Datasphere and from BW, govern access in the BDC catalog with terms and steward approval, install them into SAP services, and share them with Databricks, Snowflake, and Google BigQuery through BDC Connect. Still ahead: Data Product Studio GA (not yet confirmed), the Apache Iceberg lakehouse (GA planned for Q1 2027), and BDC data products inside Joule Studio (planned for Q1 2027).
Implication for your Datasphere work today
The semantic modeling and governance practices you build in Datasphere now form the foundation for the data products you publish in BDC. Well-designed dimensions, metrics, and access controls translate directly into well-packaged data products.
Datasphere vs Business Data Cloud: what really changed
Datasphere remains the semantic core
Datasphere's role has not changed. It is still where:
- Business meaning is modeled
- Metric definitions live
- Data governance is enforced
- Transformations are orchestrated
- Lineage and quality are monitored
Within BDC, Datasphere is where custom data products and most SAC models get their business meaning.
What changed: commercial bundling
Standalone products → Integrated platform
- Datasphere, SAC, HANA Cloud, and BW private cloud edition now licensed together through BDC
- Single capacity-unit licensing instead of separate per-product pricing
- Unified go-to-market and roadmap alignment
This is a go-to-market and licensing change, not a technical change. Datasphere functionality is unchanged.
What changed: ecosystem access
BDC Connect brings external platforms into the fold
- Zero-copy sharing to Databricks (GA Oct 2025), Snowflake (GA May 2026), and BigQuery (GA Jul 2026); Fabric in preview
- Architects can use best-of-breed tools while Datasphere owns governance
- External platforms receive data products together with their semantic metadata
This expands where Datasphere's semantic control applies, but doesn't change what Datasphere is.
What didn't change: your investment
If you have implemented Datasphere:
- Your semantic models remain valid
- Your transformation logic remains sound
- Your governance policies remain enforceable
- Your roadmap doesn't need to change today
When existing agreements end, licensing moves to BDC; tenants move over without technical migration, so the platform work is not disrupted.
Is BDC a replacement for Datasphere?
No. This is the most important clarification. Business Data Cloud is a commercial superset that includes Datasphere, not a replacement.
Datasphere ⊂ Business Data Cloud
Think of the relationship as containment: Datasphere is a core architectural component within BDC. BDC wraps Datasphere with SAC, HANA Cloud, BW private cloud edition, BDC Connect, and unified licensing.
SAP itself calls Datasphere and SAC “core component services” of BDC. You might use Datasphere without the full BDC vision (if you're only focused on semantic modeling), but the commercial direction is toward BDC as the platform.
When might you not adopt full BDC?
Organizations primarily focused on semantic modeling and governed data could theoretically stay "Datasphere-only," but:
- Since January 2026, new Datasphere licensing goes through BDC, and the BTPEA, CPEA, and pay-as-you-go route is closed
- Existing agreements run to the end of their term; tenants then move to BDC without technical migration
- SAP's product roadmap flows through BDC
In practice, BDC is the default platform. The choice is not Datasphere vs BDC; it is whether you adopt the full ecosystem (Connect, Products, etc.) or just the core (Datasphere + SAC).
What if you only want Datasphere semantics?
You can adopt BDC and focus narrowly on Datasphere's semantic layer, ignoring SAC and Connect until you need them. BDC licensing is capacity-based, so you're not forced to purchase unused features. Over time, Data Products and Connect access become more relevant as your architecture matures.
Implication for architecture decisions today
Build for Datasphere's strengths (semantic modeling, governance, data quality). Position Datasphere as the semantic foundation. Plan for BDC's future (Connect access, Data Products) without letting uncertainty paralyze present decisions.
Key architecture decisions
Should we wait for Data Products?
No. Build semantic models and governance in Datasphere now — you can already publish custom data products, and Data Product Studio, once generally available, is meant to make packaging what you've built easier. Early action on semantics pays off regardless.
Should we plan for BDC Connect?
Yes, strategically. If your architecture includes Databricks, Snowflake, or BigQuery, position Datasphere and the BDC catalog as the governance layer; BDC Connect is generally available for all three (Databricks since October 2025, Snowflake since May 2026, BigQuery since July 2026). This changes deployment decisions (which system owns the "golden" data?).
Should we commit to BDC licensing now?
Plan for it by the end of your current term. Existing BTPEA, CPEA, and pay-as-you-go agreements — including cloud credits bought before January 1, 2026 — can be used until they end, but Datasphere and SAC can't be renewed under them. Budget capacity units for that date; SAP also allows moving earlier.
Should we keep BW/4HANA?
Depends on your data warehouse role. If BW still runs core warehouse workloads, lifting it into BDC as a private cloud edition keeps it supported (BW/4HANA maintenance to 2040; BW on NetWeaver to the end of 2030) while the Data Product Generator opens its data to the rest of BDC. If you're pure semantic layer, it's optional.
Timeline and readiness
Delivered (2025–2026)
- BDC Connect for Databricks GA (October 2025)
- SAP Snowflake and BDC Connect for Snowflake GA (May 2026)
- BDC Connect for Google BigQuery GA (July 2026)
- Data product governance in the BDC catalog (September 2026)
- SAP Reltio GA inside BDC (October 2026)
Announced, not yet generally available
- BDC Connect for Microsoft Fabric (public preview)
- Data Product Studio (GA was planned for H1 2026; not confirmed)
- BDC Ontology Manager (beta planned for November 2026)
Planned for 2027
- Open lakehouse with Apache Iceberg (GA planned for Q1 2027)
- BDC data products inside Joule Studio (Q1 2027)
- BDC Connect for Amazon Athena (H1 2027)
Your readiness plan
- Budget BDC capacity units for the end of your current BTPEA, CPEA, or pay-as-you-go term
- Build Datasphere semantic foundations without waiting
- Use BDC Connect where Databricks, Snowflake, or BigQuery are already strategic
- Set up data product governance (terms, stewards) before publishing widely
Common misconceptions
- "BDC replaces Datasphere." No. Datasphere is the semantic core of BDC. The relationship is architectural containment, not replacement.
- "I have to adopt all of BDC to use Datasphere." You can focus narrowly on semantic modeling. BDC's capacity licensing means you pay for what you use, and you adopt Connect / Products when they align with your architecture.
- "BDC licensing is more expensive." It depends on your workload mix. Model your actual usage with SAP's capacity unit estimator and compare it with what you pay today, rather than assuming either outcome.
- "Data products require Data Product Studio." No. Custom data products can already be created in Datasphere and from BW and governed in the BDC catalog; Data Product Studio is still awaiting general availability, and adoption is at your pace. Existing Datasphere work continues unchanged.
- "BDC Connect forces cloud migration." Connect enables external sharing; it doesn't force you to move data. You retain control of where semantic authority lives (SAP or external platform).
Build semantic foundations and plan for BDC's ecosystem evolution
Sources
- SAP Business Data Cloud
- SAP Datasphere
- SAP and Databricks Open a Bold New Era (Feb 2025)
- SAP Business Data Cloud pricing
- Announcement: SAP Datasphere and SAP Analytics Cloud availability via SAP Business Data Cloud (SAP Community, July 2025)
- Working with Data Products in SAP Business Data Cloud Connect (SAP Help)