ServiceServiceA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPPublished 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 ASE Service
SAP ASE database systems and tenant databases on BTP with SAP running the platform operations, used from Java applications on BTP or on premise over SQL, JPA and JDBC.
The SAP ASE service gives applications on SAP BTP or on premise SAP ASE databases while SAP provides the infrastructure and the database platform operations. Through self-services the customer installs, updates and deletes SAP ASE database systems and stores data in tenant databases, separate data areas within one database system. Java applications running on SAP BTP bind to a tenant database, applications on premise consume it through Java APIs, and a developer connects to a remote database from a local machine; access is SQL, or Java through JPA and JDBC. Each of the five plans is listed in the same sixteen regions, thirteen of them marked Neo and the other three Russia (Moscow), KSA (Riyadh) and Germany (Frankfurt 4).
Retirement announcedThe regions the Discovery Center record marks as Neo, on the Large plan's Cloud Credits entitlement
This Cloud Service, in the region/data center marked as "Neo", is being removed from the Eligible Cloud Services List on December 31, 2028 ("Retired Service").SAP Discovery Center — SAP ASE Service, plan availability
Where it sits
Lives in
Provides
Database connectorsBTPDatabase connectorsConnecting 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).
Who is behind it
SAPSAPMaintains this
In the atlas: maintains 137, wrote 14@SAPmaintainer
In the atlas: maintains 137, wrote 14@SAPmaintainer
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
Connections
Group by
NodeRelationBasis
Functional
Database connectorsDatabase connectorsConnecting a data model and its queries to a databaseSAP and community, narrow by design
provides
stated
provides Database connectors
SAP ASE tenant databases that Java applications on SAP BTP bind to, managed through self-services and reached over SQL, JPA and JDBC.
“The SAP ASE service lets you consume SAP ASE databases from your applications running on SAP BTP or on-premise via Java APIs.”“Access SAP ASE tenant databases using SQL and Java (JPA and JDBC) and connect to a remote database from your local machine.”“It offers various self-services, for example, that let you create or update databases, while SAP is providing infrastructure and database platform operations.”“Install, update and delete SAP ASE database systems and store data in tenant databases to separate data areas within one database system.”“Bind your Java applications running on SAP BTP to your SAP ASE tenant databases.”“SAP (Neo) / SAP / US East (Ashburn, Neo); SAP (Neo) / SAP / Australia (Sydney, Neo); SAP (Neo) / SAP / US West (Chandler, Neo); SAP (Neo) / SAP / Europe (Rot, Neo); SAP (Neo) / SAP / US East (Sterling, Neo); SAP (Neo) / SAP / Europe (Frankfurt, Neo); SAP (Neo) / SAP / Canada (Toronto, Neo); SAP (Neo) / SAP / Brazil (São Paulo, Neo); SAP / SAP / Russia (Moscow); SAP / SAP / KSA (Riyadh); SAP (Neo) / SAP / US West (Colorado Springs, Neo); SAP (Neo) / SAP / UAE (Dubai, Neo); SAP (Neo) / SAP / Europe (Amsterdam, Neo); SAP (Neo) / SAP / Japan (Tokyo, Neo); SAP (Neo) / SAP / China (Shanghai, Neo); SAP / SAP / Germany (Frankfurt 4)”“SAP (Neo) / SAP / Europe (Rot, Neo); SAP (Neo) / SAP / US East (Sterling, Neo); SAP (Neo) / SAP / Australia (Sydney, Neo); SAP (Neo) / SAP / US East (Ashburn, Neo); SAP (Neo) / SAP / US West (Chandler, Neo); SAP (Neo) / SAP / Europe (Amsterdam, Neo); SAP (Neo) / SAP / Europe (Frankfurt, Neo); SAP (Neo) / SAP / Japan (Tokyo, Neo); SAP / SAP / Russia (Moscow); SAP (Neo) / SAP / Brazil (São Paulo, Neo); SAP (Neo) / SAP / UAE (Dubai, Neo); SAP (Neo) / SAP / Canada (Toronto, Neo); SAP / SAP / KSA (Riyadh); SAP (Neo) / SAP / US West (Colorado Springs, Neo); SAP (Neo) / SAP / China (Shanghai, Neo); SAP / SAP / Germany (Frankfurt 4)”“SAP (Neo) / SAP / US West (Chandler, Neo); SAP (Neo) / SAP / US East (Ashburn, Neo); SAP (Neo) / SAP / US East (Sterling, Neo); SAP (Neo) / SAP / Australia (Sydney, Neo); SAP (Neo) / SAP / Europe (Rot, Neo); SAP (Neo) / SAP / Canada (Toronto, Neo); SAP (Neo) / SAP / Japan (Tokyo, Neo); SAP / SAP / Russia (Moscow); SAP (Neo) / SAP / US West (Colorado Springs, Neo); SAP (Neo) / SAP / Brazil (São Paulo, Neo); SAP (Neo) / SAP / Europe (Amsterdam, Neo); SAP (Neo) / SAP / UAE (Dubai, Neo); SAP (Neo) / SAP / Europe (Frankfurt, Neo); SAP / SAP / KSA (Riyadh); SAP (Neo) / SAP / China (Shanghai, Neo); SAP / SAP / Germany (Frankfurt 4)”“SAP (Neo) / SAP / US East (Ashburn, Neo); SAP (Neo) / SAP / Europe (Rot, Neo); SAP (Neo) / SAP / US West (Chandler, Neo); SAP (Neo) / SAP / Australia (Sydney, Neo); SAP (Neo) / SAP / US East (Sterling, Neo); SAP (Neo) / SAP / Brazil (São Paulo, Neo); SAP (Neo) / SAP / US West (Colorado Springs, Neo); SAP (Neo) / SAP / Europe (Amsterdam, Neo); SAP (Neo) / SAP / Canada (Toronto, Neo); SAP (Neo) / SAP / Europe (Frankfurt, Neo); SAP / SAP / Russia (Moscow); SAP / SAP / KSA (Riyadh); SAP (Neo) / SAP / Japan (Tokyo, Neo); SAP (Neo) / SAP / UAE (Dubai, Neo); SAP (Neo) / SAP / China (Shanghai, Neo); SAP / SAP / Germany (Frankfurt 4)”“SAP (Neo) / SAP / US East (Ashburn, Neo); SAP (Neo) / SAP / US West (Chandler, Neo); SAP (Neo) / SAP / Europe (Rot, Neo); SAP (Neo) / SAP / Australia (Sydney, Neo); SAP (Neo) / SAP / US East (Sterling, Neo); SAP (Neo) / SAP / Canada (Toronto, Neo); SAP (Neo) / SAP / Brazil (São Paulo, Neo); SAP / SAP / KSA (Riyadh); SAP (Neo) / SAP / US West (Colorado Springs, Neo); SAP (Neo) / SAP / UAE (Dubai, Neo); SAP (Neo) / SAP / Europe (Frankfurt, Neo); SAP / SAP / Russia (Moscow); SAP (Neo) / SAP / Europe (Amsterdam, Neo); SAP (Neo) / SAP / Japan (Tokyo, Neo); SAP (Neo) / SAP / China (Shanghai, Neo); SAP / SAP / Germany (Frankfurt 4)”
Connecting a data model and its queries to a database
Download
Others providing
Compare all 26 on the Database connectors page →Database connectorsDatabase connectorsConnecting 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.SAP and community, narrow by design
- 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, btpManaged SAP HANA database service on BTPfrom BTP/BAIP
- SAP HANA Service (SAP Regions) for SAP BTPSAP HANA Service (SAP Regions) for SAP BTPManaged SAP HANA 2.0 database systems in fixed sizes from 64 GB to 1 TB, in SAP's own regions, with tenant databases bound to applications on SAP BTP.sap official, btpManaged SAP HANA 2.0 databases in fixed sizes on SAP BTPfrom BTP/BAIP
- PostgreSQL on SAP BTP, hyperscaler optionPostgreSQL on SAP BTP, hyperscaler optionA managed PostgreSQL from the underlying hyperscaler — AWS, Azure, Google Cloud or Alicloud — consumed through a BTP service binding.sap official, btpManaged PostgreSQL from the hyperscaler via a BTP service bindingfrom BTP/BAIP
- com.sap.cds:cds-feature-hanacom.sap.cds:cds-feature-hanaThe CAP Java feature that wires a Maven application to SAP HANA Cloud, the production default among CAP's supported databases.sap official, capSAP HANA Cloud datasource for CAP Java applicationsfrom CAP
- com.sap.cds:cds-feature-jdbccom.sap.cds:cds-feature-jdbcConnects the CAP Java runtime to JDBC databases through the CDS4j JDBC runtime: H2 and SQLite, which capire names for local development and CI tests rather than enterprise use.sap official, capJDBC runtime for H2 and SQLite in CAP Javafrom CAP
- com.sap.cds:cds-feature-postgresqlcom.sap.cds:cds-feature-postgresqlThe CAP Java feature that wires a Maven application to PostgreSQL as its datasource beside SAP HANA, with limitations capire lists: schema evolution first, and no multitenancy or extensibility yet.sap official, capPostgreSQL datasource for CAP Java applicationsfrom CAP
- com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versionsfrom CAP
- @cap-js/db-service@cap-js/db-serviceThe base every CAP database service is built on: the shared query translation and pooling that SQLite, PostgreSQL and HANA specialise rather than reimplement.sap official, capBase service shared by CAP's SQLite, PostgreSQL and HANA servicesfrom CAP
- @cap-js/hana@cap-js/hanaThe HANA database service — the production default, on the same streamlined architecture as the SQLite and PostgreSQL services.sap official, capSAP HANA database service for CAPfrom CAP
- @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, capPostgreSQL database service for CAPfrom CAP
- @cap-js/sqlite@cap-js/sqliteThe SQLite service, in memory during the inner loop — which is why a CAP project runs before anyone has provisioned a database.sap official, capSQLite database service for CAP, in memory during developmentfrom CAP
- cap-postgres-btp-connectivitycap-postgres-btp-connectivityConnects a CAP Node.js application to a PostgreSQL database that is not publicly reachable, tunnelling through BTP Connectivity and the Cloud Connector.independent, capTunnels CAP Node.js to a private PostgreSQL via Cloud Connectorfrom CAP
- cds-mongodbcds-mongodbMongoDB as a native CAP database service, through Mongoose — CQN reads and writes, managed associations as ObjectId references, $expand resolved by populate, and cds deploy --to mongoose.independent, capMongoDB as a CAP database service through Mongoosefrom CAP
- @cds-pgroll/postgres@cds-pgroll/postgresThe destructive half of PostgreSQL schema evolution — DROP and RENAME, which CAP's own schema_evolution: alter will not perform — driven from the command line beside @cap-js/postgres.independent, capCLI for DROP and RENAME schema changes beside @cap-js/postgresfrom CAP
- hdbhdbSAP's HANA driver for Node.js, written entirely in JavaScript so installing it pulls in no native client, running SQL against SAP HANA and SAP HANA Cloud with streams and prepared statements.sap official, btpPure JavaScript SAP HANA driver for Node.jsfrom BTP/BAIP
- @neoimpulse/cap-js-restore-model-defined-types@neoimpulse/cap-js-restore-model-defined-typesA CAP plugin that casts values back to the types the CDS model declares after a READ, for the entities you name, where the database driver returned them as strings.independent, capCAP plugin casting read values back to CDS model typesfrom CAP
- @quadrio/cds-db2@quadrio/cds-db2A DB2 adapter for CDS, so a CAP model can be deployed to and served from DB2, last released July 2023 and still on npm while the repository it was published from has been deleted.independent, capDB2 adapter for CDSfrom CAP
- @sap/cds-hana@sap/cds-hanaThe SAP Cloud Application Programming Model's database adapter for SAP HANA, the package a CAP project adds to run its model on a SAP HANA database.sap official, capDatabase adapter for SAP HANA in CAPfrom CAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtimefrom CAP
- @sap/hana-client@sap/hana-clientSAP's own Node.js driver for SAP HANA: connect, run SQL and prepared statements, synchronously, through callbacks or as promises, over native client libraries npm installs per platform.sap official, btpSAP's Node.js driver for SAP HANAfrom BTP/BAIP
- 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, btpSAP's relational database platform, on-premise and in HANA Cloudfrom BTP/BAIP
- SAP-samples/hana-hdbext-promisfied-exampleSAP-samples/hana-hdbext-promisfied-examplePromise-based wrappers around the SAP HANA client libraries for Node.js, Go and Python, replacing nested callbacks with a single async call.sap official, btpPromise-based wrappers around the SAP HANA client librariesfrom BTP/BAIP
- cds-pgcds-pgA PostgreSQL adapter for SAP CDS, built by the SAP Mentors community, which gave CAP a Postgres persistence option years before @cap-js/postgres shipped.independent, capPostgreSQL adapter for SAP CDS from the SAP Mentors communityfrom CAP
- cap-snowflakecap-snowflakeA CAP database adapter for Snowflake with OData V4 support, which the maintainer marks as early development, so its contract is expected to move.independent, capCAP database adapter for Snowflake with OData V4 supportfrom CAP
- cds-mysqlcds-mysqlA MySQL and MariaDB database adapter for CAP that connects to a database instance and translates incoming CQL/CQN requests to it; the repository the package declares has been deleted.independent, capMySQL and MariaDB database adapter for CAPfrom CAP
Details
Sources
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 atlas
- First seen.
For your agent
- Ref
artifact:btp-ase- JSON
- /artifacts/btp-ase.json
- MCP
- Connecting an agent