Skip to main content
Integrations · SAP HANA

Point it at SAP HANA.
Walk away with insights.

DecisionBox connects to your SAP HANA database — HANA Cloud or on-premise HANA 2.0 — read-only, scoped by the role you choose. The agent reads your schemas in place, validates the SQL it writes before it runs, and surfaces validated insights from what is already in your database. An Enterprise connector.

SAP HANA SQLRead-onlySAP HANA CloudHANA 2.0 (on-prem)
Read-only by design

Scoped to the role you choose.

DecisionBoxagentSAP HANAyour databaseRoleANALYST_ROSchemaANALYTICSread-onlyRead-only query
Easy and low-effort to integrate

Three things to know on day one.

Read-only, scoped by your HANA role

The agent connects with a HANA user and role you choose — a read-only role with access to just the schemas you want it to see. Your HANA authorization model is the access boundary; the agent cannot reach anything the role does not grant.

Reads your schemas in place

No tables to refactor, no pipeline to stand up, no database-side changes. The agent discovers your existing schemas on its first run, re-checks them on every run after, and samples rows safely to learn the shape of your data.

Validates SQL before it runs

Every generated query is checked for validity against your schema before it runs. Nothing is executed against your data until it has been verified as a safe, read-only query.

Authentication

Two ways in. Both standard HANA.

Pick the one that matches how you already hand SAP HANA credentials to the rest of your stack. Both end at the same read-only role and schema you configured — what changes is whether you fill in the connection fields one at a time or paste a full connection string.

Quick start

Username / Password

Add the host, port, and a read-only HANA user in the project config — works for SAP HANA Cloud and on-prem HANA 2.0, including users backed by LDAP. The credential is stored encrypted and never written to logs.

Advanced

Connection string

Paste a full HANA connection string instead — for a specific instance, tenant database, or any setup that needs extra connection parameters. The role you sign in as is still the boundary.

Both options end at the same read-only HANA role and schema you configured — and nothing more. If your security team has already approved how the rest of your stack talks to HANA, they have already approved DecisionBox.

One platform, your whole estate

An Enterprise connector, on the same engine.

Part of DecisionBox Enterprise

The SAP HANA connector ships with DecisionBox Enterprise, alongside SSO, data governance, audit logging, and the other capabilities your security and compliance teams expect. Same autonomous discovery agent, run against HANA.

See all enterprise features

Not locked to SAP HANA

BigQueryRedshiftSnowflakePostgresDatabricksMSSQLOracleEnterpriseSAP HANAEnterprise

The same agent runs against any of them. If your warehouse moves, your DecisionBox install moves with it.