Database connectors
Which database the model actually runs on, and what changes when it is not the default one — the choice that is invisible until a query behaves differently. HANA Cloud is the default under a CAP application: HDI containers, calculation views, and the features the core reaches for first. PostgreSQLPostgreSQLA relational database. For CAP it is the production database when the answer is not HANA, reached through an adapter that translates CDS queries into its SQL. through @cap-js/postgres@cap-js/postgresThe PostgreSQL database service — the production option for running CAP off HANA, sharing the base service with the other three.sap official, cap is the alternative when the answer is not HANA, with its own schema evolution and no HDI.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Overview
Auto-configures the default Persistence Service from a bound SAP HANASAP HANASAP’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.sap official, btp service instance so a CAP Java application runs against SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp; without a matching binding it deactivates and the stack falls back to H2 for local development.
Connects CAP Java's persistence layer to H2 and SQLiteSQLiteAn embedded SQL database engine used as a selectable local cache store by CAP caching plugins. over JDBC. capire names local development and CI tests as their use and states that neither is an enterprise grade database.
Auto-configures the default Persistence Service from a bound PostgreSQLPostgreSQLA relational database. For CAP it is the production database when the answer is not HANA, reached through an adapter that translates CDS queries into its SQL. instance so a CAP Java application runs against PostgreSQL instead of SAP HANASAP HANASAP’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.sap official, btp, with known limitations in schema evolution and no multitenancy or extensibility support yet.
Creates a CQN-based Persistence Service from the configured datasource for SAP HANA, PostgreSQL, H2 or SQLite, and serves it as the database client.
A Java coverage assessment has not been written. View all flavors
No community artifact is confirmed here for Java.
A Java coverage assessment has not been written. View all flavors
Licence
LicenceSAP Developer License Agreement 3.2 CAP§ 1AlwaysA 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 →Artifacts
Details
Coverage
For your agent
- Ref
capability:database-connectors- JSON
- /capabilities/database-connectors.json
- MCP
- Connecting an agent