Add a SAP HANA Source Datastore

A source datastore is a storage location Qualytics connects to so it can profile, scan, and monitor data. Adding SAP HANA as a source lets Qualytics query your HANA tables and views through the SAP HANA JDBC driver and run quality operations on the schemas it discovers.

Before you start, review the SAP HANA Permissions and the Authentication pages.

Tip

SAP HANA can also be used as an enrichment datastore. Link a separate enrichment datastore during creation via Link Enrichment on Datastore Creation, or afterwards via Link Enrichment Datastore.

This page covers two ways to add a SAP HANA source datastore: using a new connection or reusing a saved one. Both flows share the same form fields. Use the tabs in Field reference below to pick the flow that matches your situation. If this is your first SAP HANA datastore in Qualytics, use the New Connection tab.

For the generic step-by-step walkthrough of the Add Source Datastore modal (open it, toggle the connection mode, test, finish), see Add Source Datastore. The fields described below apply to the SAP HANA-specific portion of that flow.

Field reference

The Add Source Datastore form changes depending on whether you create a new connection or reuse a saved one. Pick the tab below that matches your flow.

New ConnectionExisting Connection

When Add New Connection is toggled ON, the form shows four groups of fields: Connection Properties, Secrets Management (optional Vault integration), Datastores Extraction, and Datastore Properties.

Connection Properties

These fields define the SAP HANA endpoint and the credentials the connection uses.

REF.	FIELD	REQUIRED	DESCRIPTION
1	Connection Name	Yes	A label for the saved connection (e.g., acme_hana_prod). Appears in the Connection dropdown when you create future datastores.
2	Host	Yes	The HANA endpoint. For HANA Cloud, the URL provided by SAP (e.g., xxxxxxxx.hna1.prod-us10.hanacloud.ondemand.com). For on-premises, the hostname or IP of the HANA system.
3	Port	Yes	The HANA SQL port. Defaults to 443. For on-premises HANA, override to 3<instance>15 (commonly 39015) or the tenant-specific port.
4	Username	Yes	The HANA database user with SELECT privileges on the target schema.
5	Password	Yes	The HANA user password. Stored encrypted; never echoed back.

Tip

For the exact HANA privileges Qualytics needs, see SAP HANA Permissions.

Secrets Management (optional)

Use this group only if you want Qualytics to pull credentials from HashiCorp Vault instead of typing them into the form. Toggle HashiCorp Vault ON to expose the fields below.

REF.	FIELD	REQUIRED	DESCRIPTION
1	Login URL	Yes	The Vault endpoint Qualytics uses to authenticate (e.g., https://vault.example.com/v1/auth/approle/login).
2	Credentials Payload	Yes	A JSON body containing the credentials Vault expects (e.g., {"role_id":"...","secret_id":"..."}).
3	Token JSONPath	Yes	The JSONPath that extracts the client token from Vault's response. Defaults to $.auth.client_token.
4	Secret URL	Yes	The Vault path where the secret is stored (e.g., https://vault.example.com/v1/secret/data/sap-hana).
5	Token Header Name	Yes	The HTTP header name used to send the token. Defaults to X-Vault-Token.
6	Data JSONPath	Yes	The JSONPath that extracts the secret payload from Vault's response. Defaults to $.data.

Note

Once Vault is configured, reference any secret value in the Connection Properties fields using ${key} (e.g., ${password}). Qualytics resolves the secret at the moment the connection is opened, so rotated values take effect on the next connection.

Datastores Extraction

Pick the tenant database (when applicable) and the schema(s) Qualytics should read from.

REF.	FIELD	REQUIRED	DESCRIPTION
1	Database	No	The HANA tenant database name. Leave blank for HANA Cloud (the tenant is encoded in the hostname). For on-premises multi-tenant deployments, type or pick the tenant database.
2	Schema	Yes	One or more HANA schemas inside the tenant. Each schema you pick becomes its own datastore. Click the refresh icon to load the available schemas.

Datastore Properties

Common fields for every source datastore, visible below the Datastores Extraction section in the same form.

REF.	FIELD	REQUIRED	DESCRIPTION
1	Name Template	No	Defines the naming pattern for each source datastore being created. Use {{ schema }} as a placeholder that gets replaced with the actual schema name (e.g., hana_{{ schema }} becomes hana_sales).
2	Group	No	Organizes your datastores under a shared group in the navigation tree. Select an existing group or create a new one with the Add New Group toggle.
3	Teams	Yes	Select one or more teams to associate with this source datastore.
4	Initiate Sync	No	Automatically sync the datastore to detect containers and fields after creation.

Below the form fields, the modal shows a Connection Info banner with the resolved IP address and a Test Connection button to verify credentials before clicking Finish or Next.

When Add New Connection is toggled OFF and you pick a saved SAP HANA connection, the Connection Properties and Secrets Management sections are collapsed and read-only: Qualytics has already validated those credentials, so there is nothing for you to fill in. You only fill in the Datastores Extraction and Datastore Properties below.

To change a saved connection's credentials, edit the connection itself from Settings → Connections. Edits there apply to every datastore that reuses the connection.

Datastores Extraction

REF.	FIELD	REQUIRED	DESCRIPTION
1	Database	No	The HANA tenant database name. Leave blank for HANA Cloud. For on-premises, type or pick the tenant database.
2	Schema	Yes	One or more HANA schemas inside the tenant. Each schema becomes its own datastore. Click the refresh icon to load the available schemas.

Datastore Properties

The remaining fields (Name Template, Group, Teams, Initiate Sync, plus the Connection Info banner and Test Connection button) work the same as in the New Connection flow above. See the Datastore Properties table on the New Connection tab of the Field reference.