Scenario Some organizations have non-SAP data (e.g., from third-party apps, IoT sources, data lakes) that they want to retain in Databricks rather than moving everything into SAP’s environment. In the new SAP Business Data Cloud (BDC) architecture, SAP offers an integrated “SAP Databricks” service (an OEM version of Databricks) that seamlessly connects with BDC. This setup allows you to:
In SAP Business Data Cloud, SAP data is stored in HANA Cloud Data Lake files (an object store) and managed via foundation services. For Databricks, the data typically resides in:
A key feature in the BDC–Databricks partnership is Delta Sharing or “zero-copy sharing,” which allows you to provide read access to data without physically replicating it. So if a data set is stored in Databricks, you can make it visible to SAP Business Data Cloud analytics or AI use cases, and vice versa, without having to manage multiple data copies.
When you have non-SAP data that needs to be ingested into Databricks, you can use:
In short, if your architecture calls for certain data sets to remain in Databricks, you can do so without losing out on SAP’s built-in analytics, AI, and business semantic features. Data is stored in Delta Lake within Databricks, and you can bring in non-SAP data using any Databricks-supported ingestion method or standard ETL/ELT tools. Once in Databricks, that data can still be surfaced in SAP Business Data Cloud for unified insights, all while retaining the power of Databricks for big data processing and machine learning.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 47 | |
| 21 | |
| 19 | |
| 18 | |
| 16 | |
| 13 | |
| 12 | |
| 11 | |
| 11 | |
| 11 |