Integrations · Databases · Coming next

SAP HANA: coming next connector

SAP HANA (Cloud and on-premises) connector using SAP's driver installed by the customer: SYS catalog discovery, primary and foreign keys, M_TABLES row estimates, bounded profiles and reads into the local engine, over verified TLS by default.

Coming next Databases

Active implementation; not yet available for production use.

Customer-installed driver. The SAP HANA driver (hdbcli 2.30.27) is licensed by its vendor under the SAP Developer License Agreement (or your SAP agreement), which does not allow DataNivra to redistribute it, so the standard agent image does not include it. You install it by building the agent extension image; building it means you accept that licence.

Not available yet. Active implementation; not yet available for production use. The console does not offer it, and asking an agent for a connector it does not ship fails with the error code CONNECTOR_NOT_AVAILABLE; the product never fakes a connection.

What you can do today

Export tables to Parquet or CSV inside your network and read them with the shipped Local files, Amazon S3 / S3-compatible or Azure Blob / Data Lake connectors.

Whatever route you choose, the export and every row-level step stay inside your network. You can evaluate the whole workflow now with the synthetic demo.

Known limitations

  • Customer-installed driver: the standard agent image does not include hdbcli. Build the DataNivra agent extension image (agent/runtime/extensions/sap-hana), which installs hdbcli under the SAP Developer License Agreement or your own SAP agreement; without it the agent reports CONNECTOR_NOT_AVAILABLE.
  • Database user and password only (no X.509, JWT, SAML or Kerberos authentication).
  • Calculation views with input parameters are not read.
  • Not yet run against a real SAP HANA system (HANA express needs more memory than the test host has).

Capability matrix

SAP HANA does not ship yet, so no capability is verified. The column shows what the design plans; plans are not commitments.

Capabilities of SAP HANA
CapabilityDesign intent
DiscoveryPlanned
ClassificationPlanned
ProfilingPlanned
MaskingPlanned
Deterministic maskingPlanned
Entity-aware subsettingPlanned
Relationship preservationPlanned
Synthetic workflowsNot planned yet
CertificationPlanned
ProvisioningPlanned
CI/CDNot planned yet
Evidence generationPlanned

How the connector is designed to prove read-only access

Proven from SYS.EFFECTIVE_PRIVILEGES for the connecting user (direct, role and PUBLIC grants) before reading: object privileges must be SELECT (or SELECT METADATA, REFERENCES, UNMASKED), EXECUTE is tolerated on SAP-maintained schemas only, and the only system privilege tolerated is CATALOG READ; DATA ADMIN and every write or DDL privilege refuse the source.

Customer-installed driver: SAP's licence for hdbcli does not allow DataNivra to redistribute it, so you build DataNivra's extension image, which installs the pinned driver on top of a released agent image under SAP's licence terms that you accept. encrypt and sslValidateCertificate default to true.

Planned authentication: database user and password (secret reference).

What crosses the boundary

Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:

  • Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
  • Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
  • Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
  • Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.

Never sent:

  • Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
  • Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
  • Free text copied from your data, or exception messages that contain values.

See the customer-resident architecture and how to verify these claims yourself.

Request this connector

We prioritise connectors by demand, engineering effort and strategic fit. Telling us that SAP HANA matters to you is counted; it does not commit a delivery date.

We only ask which connector, your company size and your industry. Never send credentials, connection details, schemas or data through this form.

Only if you want us to tell you when the status of SAP HANA changes.

Need something specific from the SAP HANA connector? Request a feature (please describe it without real data).

All integrations · Database test data management · Guides · Start free