@sap/hana-client
SAP'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.
Reaching SAP HANA from Node.js with no framework database layer in between: a connection is opened with connect, statements run with exec, and prepare returns a statement executed with parameters, the same calls available synchronously, through callbacks, or as promises through the package's own extension/Promise.js module. Connection details are passed to the call or taken from a key in the hdbuserstore, so a host, port and password need not sit in the source. The driver is not JavaScript alone: it contains native libraries, npm downloads the ones for every available platform on install, the Node.js driver shipped with the SAP HANA client is 64-bit only, and that client install carries the same driver for a machine that already has it. In a CAP project it is not what runs unless it is asked for, since @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, cap uses hdb by default and adding this package to the dependencies takes precedence over that.
Facts
Where it sits
Who is behind it
In the atlas: maintains 137, wrote 14@SAPmaintainer
Before choosing this
Conditions
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
- Package
- Origin
- By SAP
- Runtime
- Node.js
As a package
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Connecting a data model and its queries to a database
SAP HANA database service for CAP
MCP proxy pinning an agent's ABAP tools to one SAP system
Download
Install
npm add @sap/hana-clientDerived from the package name. No recipe recorded; the README has the configuration.
History
v2.30.27
v2.30.24
v2.29.27
v2.29.25
v2.29.23
v2.28.22
v2.28.21
v2.28.20
v2.28.19
v2.28.17
v2.27.24
v2.27.23
v2.27.19
v2.26.26
v2.26.25
v2.26.18
v2.25.31
v2.25.29
v2.25.22
v2.24.26
v2.24.24
v2.24.21
v2.23.27
v2.23.26
v2.23.24
v2.22.32
v2.22.29
v2.22.27
v2.21.31
v2.21.28
v2.21.26
v2.20.23
v2.20.22
v2.20.20
v2.20.15
v2.19.21
v2.19.20
v2.19.18
v2.18.27
v2.18.24
v2.18.22
v2.17.22
v2.17.21
v2.17.14
v2.16.26
v2.16.21
v2.15.22
v2.15.19
v2.15.17
v2.14.24
v2.14.23
v2.14.22
v2.14.18
v2.13.22
v2.13.21
v2.13.13
v2.12.25
v2.12.22
v2.12.20
v2.12.13
v2.11.20
v2.11.14
v2.10.20
v2.10.15
v2.10.13
v2.10.9
v2.9.28
v2.9.23
v2.9.19
v2.8.22
v2.8.20
v2.8.16
v2.7.26
v2.7.23
v2.7.21
v2.7.16
v2.6.64
v2.6.61
v2.6.58
v2.6.54
v2.5.111
v2.5.109
v2.5.105
v2.5.104
v2.5.101
v2.5.86
v2.4.202
v2.4.196
v2.4.167
v2.4.162
v2.4.155
v2.4.151
v2.4.144
v2.4.142
v2.4.139
v2.4.126
v2.3.144
v2.3.134
v2.3.130
v2.3.123
v2.3.119
v2.3.112
v2.3.106
v2.3.21
v2.4.194
v2.4.191
v2.4.182
v2.4.177
v2.4.171
Others providing
Compare all 22 on the Database connectors page →- 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 BTP
- 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 binding
- 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 applications
- 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 Java
- 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 applications
- 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 versions
- @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 services
- @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 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 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 development
- 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 Connector
- 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 Mongoose
- @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/postgres
- @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 types
- @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 CDS
- @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 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 runtime
- 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 Cloud
- 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 community
- 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 support
- 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 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
History in the atlas
- First seen.
For your agent
- Ref
artifact:sap-hana-client- JSON
- /artifacts/sap-hana-client.json
- MCP
- Connecting an agent