SAP HANA Overview

Prizm connects to SAP HANA directly over SQL, whether it runs on-premises, on a self-hosted VM, or as SAP HANA Cloud. Once connected, Prizm catalogs the tables and columns in the schemas you choose, profiles them, and tracks volume, freshness, and schema changes.

​

Why Connect SAP HANA to Prizm?

Catalog & Context Prizm discovers the schemas, tables, and columns you include in scope and adds them to the Prizm catalog as table assets, with each column’s HANA data type. Data Quality Metrics run against the included tables and columns, and every asset gets a quality score, alerts, and issues like any other Prizm source. Observability Each table shows its volume (record count), freshness, and schema, and schema changes are flagged on the asset. Criticality Tables are assigned a criticality tier (for example Low or Medium) using the same scoring framework as other Prizm connectors.

​

What Prizm Can Do After Connecting

• Discover schemas, tables, views, and columns.
• Run Operational jobs: metadata refresh, schema change detection, and freshness-style observability.
• Run Profile and Structural (quality) metrics on the assets you select.
• Run Business metrics, including comparison and reconciliation metrics that use Spark.
• Support governance workflows on catalog assets, such as terms and recommendations where enabled.
• Generate AI-assisted insights on configured metrics and assets.

​

A Schema-Scoped Catalog

SAP HANA has no separate database layer in Prizm. The catalog is schema-first, and assets are named with slashes: SCHEMA/TABLE for tables and SCHEMA/TABLE/COLUMN for columns. The setup wizard has no database picker.

​

Authentication

SAP HANA connections authenticate with a Username and Password. Turning on Use Vault replaces those fields with a Select Vault dropdown, which lists the vault instances your organization has already configured (HashiCorp Vault, Azure Key Vault, or AWS Secrets Manager), plus a Key field for the credential’s location in that vault. See Setup for the full walkthrough.

​

Scoping a Connection

Two optional controls limit what Prizm reads:

• Schema Owner (on the connection form) filters schemas by their owner, using SYS.SCHEMAS.SCHEMA_OWNER. It is not a database name.
• Include / Exclude (on the configuration step) selects the schemas and tables or views to profile, and any to leave out. Wildcards are supported where configured.

​

Schema Change Detection

Prizm detects schema changes by comparing catalog snapshots on each operational run. It doesn’t need SAP HANA audit tables.

​

Comparison Metrics and Storage

Comparison (reconciliation) metrics can run on Spark and read SAP HANA over JDBC. A Spark cluster is recommended when you compare at scale. Prizm platform storage, set in your organization’s platform settings, is required for exceptions and large comparison results. See Setup.

​

Supported SAP HANA Objects

​

Current Scope

This connector is read-only. Prizm never writes to your SAP HANA system. The following are not part of the current connector: SAP RISE and S/4HANA Cloud (these managed environments don’t expose direct database access), a separate asset type for Calculation Views (they appear as plain views), stored procedures, lineage, usage analytics (the SQL plan cache is in memory and volatile, so usage can’t reach parity with other sources), and authentication methods other than username and password.

​

Next Steps