PlatformPlatformtypeDelivered with a runtime rather than published. Nothing versions it independently and there is nothing to adopt or avoid — it is simply what the platform gives you.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

SAP HANA

SAP’s relational database platform, which stores application data and executes SQL and SQLScript in the database, available on-premise and as the managed service SAP HANA Cloud.

Stores application data and executes SQL and SQLScript in the database. On ABAP, AMDP procedures and functions execute SQLScript on SAP HANA. SAP HANA Cloud is the managed cloud service; SAP HANA also exists as an on-premise database.

Where it sits

Lives in
Provides
Database connectorsCAPBTPABAPDatabase connectorscapabilityConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).
Serves

Before choosing this

Conditions

PracticalFunctional boundary

For provisioning a managed database on BTP, see SAP HANA Cloud. Features differ between HANA versions; an on-premise deployment and a cloud instance are not interchangeable without compatibility checks.

LicenceSAP Developer License Agreement 3.2 CAP§ 1from Database connectorsA covered CAP application uses a connector to copy or persist SAP product data in a non-SAP database product.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.

The connector itself does not decide the licence boundary. Section 1 makes the destination and purpose of extraction relevant, including the scoped exception for interoperability with an SAP product.

SAP Developer License Agreement 3.2 CAP →

What it declares

Every artifact

Type
Platform
Origin
By SAP

Connections12

SAP HANA connectionsSAP HANAPROVIDES→ provides1provides stated Provides the SQL database applications connect to, including on-premise HANA deployments. SQLScript procedures and functions execute in the database; ABAP can manage and call them through AMDP. SAP — Migrate to SAP HANA Cloud from SAP HANA Platform: https://developers.sap.com/tutorials/hana-cloud-migration/ SAP ABAP cheat sheets — AMDP: https://github.com/SAP-samples/abap-cheat-sheets/blob/main/12_AMDP.mdDatabase connectorsUSED BY← connected from4connected from derived Connecting on-premises database or BI tools to [SAP HANA](artifact:sap-hana) databases running on SAP BTP. Through: inverted from its connects edge https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/cloud-connector: https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/cloud-connectorCloud Connectorconnected from derived running the application's standard SQL and its geospatial queries against the HANA instance named in the JDBC connection properties of the Maven build. Through: inverted from its connects edge SAP-samples/hxe-hibernate-google-app-engine — README: https://github.com/SAP-samples/hxe-hibernate-google-app-engine SAP-samples/hxe-hibernate-google-app-engine — README, Adjust the JDBC connection data: https://github.com/SAP-samples/hxe-hibernate-google-app-enginehxe-hibernate-google-app-engineconnected from derived If: `STG_DB=hana` selects HANA as the backend Open SQL and AMDP bodies run against a real HANA through the eleven-method database seam, over the npm driver `hdb` Through: inverted from its connects edge open-steamgate — docs/db-backends.md, the HANA client: https://raw.githubusercontent.com/oisee/open-steamgate/main/docs/db-backends.md open-steamgate — docs/db-backends.md, what a remote database costs: https://raw.githubusercontent.com/oisee/open-steamgate/main/docs/db-backends.mdopen-steamgateifconnected from derived If: the HANA adapter is configured; the OData client reaches a service instead Reads the rows a recipe allow-lists by running a parameterised SELECT and streaming it in bounded pages, over a certificate-validated connection. Through: inverted from its connects edge yassinbahri/sap-knowledge-pipeline — README: https://raw.githubusercontent.com/yassinbahri/sap-knowledge-pipeline/main/README.md yassinbahri/sap-knowledge-pipeline — README: https://raw.githubusercontent.com/yassinbahri/sap-knowledge-pipeline/main/README.mdsap-knowledge-pipelineif← needed by1needed by derived the database the SQL files are run against: the HANA tenant the S/4HANA system uses. Through: inverted from its requires edge SAP-samples/s4hana-hana-audit-policies — README, Description: https://github.com/SAP-samples/s4hana-hana-audit-policiess4hana-hana-audit-policies← optionally used by4optionally used by derived If: When store: "hana" is selected. Cache storage through keyv-hana; other store modes do not require this backend. Through: inverted from its requires edge cds-caching — Store Types: https://github.com/mikezaschka/cds-caching/blob/main/README.mdcds-cachingifoptionally used by derived If: `STG_DB=hana` selects HANA as the backend the data layer when an AMDP body is to run where it belongs and `sy-dbsys` is to read HDB; the maintainer records it as an option and never the default, and HANA Express is the image the compose file starts Through: inverted from its requires edge oisee/open-steamgate — README, AMDP and SQLScript: https://github.com/oisee/open-steamgate open-steamgate — docs/db-backends.md, what a remote database costs: https://raw.githubusercontent.com/oisee/open-steamgate/main/docs/db-backends.mdopen-steamgateifoptionally used by derived If: the system's database type (dbms_type) is hdb running the HANA-specific start, stop, connect and status commands when the SID's database is SAP HANA Through: inverted from its requires edge sap-basis-ops: skills/sap-db-command-reference/SKILL.md: https://raw.githubusercontent.com/adam0thman/sap-basis-ops/main/skills/sap-db-command-reference/SKILL.mdsap-basis-opsifoptionally used by derived If: the Recall Rescue part is run The trace: HANA Graph follows the defective cell lot through the battery genealogy, in openCypher over ADBC. Through: inverted from its requires edge Kamilkov/supply-chain-rescue — README, Recall Rescue (A4H): https://github.com/kamilkov/supply-chain-rescue Kamilkov/supply-chain-rescue — README, Recall Rescue (A4H): https://github.com/kamilkov/supply-chain-rescueSupply Chain Rescueif← used by2used by derived the database environment the samples run against; its AFL component is what ships the Predictive Analysis Library the SQL examples call. Through: inverted from its requires edge SAP-samples/hana-ml-samples — README: https://github.com/SAP-samples/hana-ml-sampleshana-ml-samplesused by derived the database the application stores its incident and address data in and runs its SQL and geospatial queries against. Through: inverted from its requires edge SAP-samples/hxe-hibernate-google-app-engine — README, Requirements: https://github.com/SAP-samples/hxe-hibernate-google-app-enginehxe-hibernate-google-app-engine

Learn more2

Readings
  1. Bridging Python and SAP HANA: Inside the sqlalchemy-hana Open-Source DialectSAP Developers, YouTube — SAP Developers playlists
  2. Analyze and optimize ABAP Cloud model apps built on core data servicesSAP TechEd — session catalogue
Database connectors
  1. SAP HANA CloudManaged SAP HANA database service on BTP
  2. PostgreSQL on SAP BTP, hyperscaler optionManaged PostgreSQL from the hyperscaler via a BTP service binding
  3. com.sap.cds:cds-feature-hanaSAP HANA Cloud datasource for CAP Java applications
  4. com.sap.cds:cds-feature-jdbcJDBC runtime for H2 and SQLite in CAP Java
  5. com.sap.cds:cds-feature-postgresqlPostgreSQL datasource for CAP Java applications
  6. com.sap.cds:cds-services-bomMaven bill of materials pinning CAP Java module versions
  7. @cap-js/db-serviceBase service shared by CAP's SQLite, PostgreSQL and HANA services
  8. @cap-js/hanaSAP HANA database service for CAP
  9. @cap-js/postgresPostgreSQL database service for CAP
  10. @cap-js/sqliteSQLite database service for CAP, in memory during development
  11. cap-postgres-btp-connectivityTunnels CAP Node.js to a private PostgreSQL via Cloud Connector
  12. cds-mongodbMongoDB as a CAP database service through Mongoose
  13. @cds-pgroll/postgresCLI for DROP and RENAME schema changes beside @cap-js/postgres
  14. @neoimpulse/cap-js-restore-model-defined-typesCAP plugin casting read values back to CDS model types
  15. @quadrio/cds-db2DB2 adapter for CDS
  16. @sap/cds-hanaDatabase adapter for SAP HANA in CAP
  17. @sap/cdsCAP Node.js runtime
  18. @sap/hana-clientSAP's Node.js driver for SAP HANA
  19. cds-pgPostgreSQL adapter for SAP CDS from the SAP Mentors community
  20. cap-snowflakeCAP database adapter for Snowflake with OData V4 support
  21. cds-mysqlMySQL and MariaDB database adapter for CAP

Details

Sources1
Added by handdiscovered herechecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, data-and-persistence
History in the atlas1
  1. First seen.
For your agent