Skip to main content
This page covers everything you need to connect SAP HANA (on-premises or SAP HANA Cloud) to Prizm: prerequisites, the permissions Prizm needs, network requirements, and the connection wizard.

Prerequisites

SAP HANA is schema-scoped. There is no separate “database” or catalog layer to choose, as there is for Snowflake. Prizm names assets with slashes: SCHEMA/TABLE for tables and SCHEMA/TABLE/COLUMN for columns.

Required SAP HANA Permissions

Give the Prizm user least-privilege access to the objects in scope. Prizm reads catalog views and runs SELECT statements (including metric queries) on the tables you monitor.

Catalog and metadata

If your SAP HANA deployment provides a catalog-read or monitoring-style role, you can grant that instead of the individual SELECT privileges above. Otherwise grant SELECT on the views listed, plus any tenant-specific statistics views your version exposes.

User data (in-scope schemas)

Optional

Example grants

The following creates a dedicated user with role-based catalog access. Adjust it to your security policy and replace <schema> with each schema you plan to include.
Prizm is read-only on SAP HANA. None of these grants allow Prizm to change data or objects.

Network and Security Checklist

Connector Setup

1

Open the connector wizard

Navigate to Source and click the + icon next to the source list. Search for SAP HANA and select it from the connector grid.
2

Enter source details

The SAP HANA Source Details form

SAP HANA source details

3

Provide credentials

Toggle Use Vault to retrieve credentials from a vault instead of entering them directly. Prizm supports HashiCorp Vault, Azure Key Vault, and AWS Secrets Manager.
The SAP HANA credential fields and optional Schema Owner

Username, password and the optional Schema Owner filter

4

Validate the connection

Click Validate (or Test connection). Prizm runs a simple query (SELECT 1 FROM DUMMY) to confirm it can connect. If you set a Schema Owner, Prizm also checks that at least one non-system schema exists for that owner.
Validation must succeed before you can click Next. If it fails, check the host, port, credentials, firewall rules, and Schema Owner value.
5

Choose what to profile

Click Next to open the source configuration step. Scope is schema-first, so there is no database selection.
6

Save

Complete the configuration. The source then appears in the Source list, where the Valid column shows a green check for a working connection. Its assets appear in the catalog once the first run completes. Filter the Asset page by SAP HANA to see them.

Run Your First Jobs

For a new source, run jobs in this order:
  1. Technical. Registers the schema assets.
  2. Operational. Discovers tables, views, and columns.
  3. Profile, Structural, and Business. Run these as needed once the assets exist.
When they complete, the catalog shows Schema → Table/View → Column. Metrics, alerts, and the schema change timeline fill in for the assets in scope, and comparison metrics run when a Spark cluster is configured.

Spark Connectivity for Comparison Metrics

Comparison and reconciliation metrics can run on Spark and read SAP HANA over JDBC. Make sure your Spark workers can reach the SAP HANA host and port, and that the credentials work from there. The connection uses the SAP JDBC driver in this form:

Next Steps

What We Collect

See what Prizm extracts from SAP HANA.

FAQ

Common questions about credentials, scoping, and permissions.

Troubleshooting

Diagnose connection failures, permission errors, and timeouts.