> ## Documentation Index > Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt > Use this file to discover all available pages before exploring further. # SAP HANA FAQ > Common questions about the SAP HANA connector. ## Connector Lifecycle > **What happens if I delete a connector?** > > Deleting a source triggers an approval workflow based on your organization's settings. Once approved, the source and all associated metadata are permanently deleted. The deletion cannot be undone after approval. > **What happens to existing data and alerts if a connector is paused or disconnected?** > > Existing metadata, quality scores, and alerts are retained while the connector is inactive. No new data is collected until the connector is re-enabled. If the connector is permanently deleted (after approval), all associated data is removed. ## SAP HANA-Specific > **Which SAP HANA deployments can I connect?** > > Self-managed SAP HANA (on-premises or on a customer-managed VM) and SAP HANA Cloud. Prizm connects over SQL, so the host and SQL port must be reachable from Prizm. > **Which port should I use?** > > Use the SQL port of your instance. The wizard defaults to `39015`. Self-managed systems typically use `315`, and SAP HANA Cloud listens on `443`. > **Which authentication methods are supported?** > > Username and password, either entered directly or retrieved from a configured vault. Other HANA methods such as Kerberos, SAML, JWT, X.509 certificates, and the HANA Secure User Store are not available in the connector today. > **What privileges does the Prizm user need?** > > Prizm needs `SELECT` on the SAP HANA catalog views it reads (`SYS.SCHEMAS`, `SYS.TABLES`, `SYS.VIEWS`, `SYS.TABLE_COLUMNS`, `SYS.VIEW_COLUMNS`, `SYS.CONSTRAINTS`, `SYS.REFERENTIAL_CONSTRAINTS`, `SYS.INDEXES`, and where available `SYS.M_TABLES` and `SYS.M_TABLE_STATISTICS`), plus `SELECT` on the tables and views in the schemas you include, and on any comparison source and target tables. A catalog-read or monitoring-style role can replace the individual view grants. No DDL privileges are required. See [Setup](/sources/sap-hana/setup#required-sap-hana-permissions). > **Why does validation fail, and why can't I click Next?** > > Prizm validates the connection by running `SELECT 1 FROM DUMMY`. If you set a Schema Owner, it also needs at least one non-system schema owned by that user. Validation must pass before the wizard moves on to scope configuration. Check the host, port, credentials, firewall rules, and Schema Owner value. > **Why isn't there a database or catalog picker?** > > SAP HANA is schema-scoped. Prizm names assets `SCHEMA/TABLE` and `SCHEMA/TABLE/COLUMN`, and scope is chosen by schema, table, and view includes and excludes. > **Do I need a Spark cluster or platform storage?** > > Platform storage is required for exceptions and large comparison results. A Spark cluster is recommended if you run comparison metrics at scale. Spark workers need network access to the SAP HANA host and port as well. > **How does Prizm detect schema changes?** > > By comparing catalog snapshots on each operational run. It doesn't require SAP HANA audit DDL tables. > **In what order should I run the first jobs?** > > Run Technical first to register schema assets, then Operational to discover tables, views, and columns, and then Profile, Structural, and Business as needed. > **How do I limit which schemas Prizm reads?** > > Use the optional **Schema Owner** field on the connection form to filter schemas by owner, and the **Include** and **Exclude** sections on the configuration step to pick specific schemas and tables or views. > **Can I connect SAP RISE or S/4HANA Cloud?** > > Not with this connector. SAP RISE environments are managed by SAP and don't expose the underlying HANA database for direct connections, so they can't be reached by a SQL connector. > **Are Calculation Views and lineage available?** > > Calculation Views appear in the catalog as plain views, with no separate asset type. Lineage isn't available, including lineage through Calculation Views, and stored procedures aren't collected. > **Does Prizm change anything in SAP HANA?** > > No. The connector is read-only. *** > **[Troubleshooting](/help/troubleshooting)** > > For connection errors, permission issues, and performance problems. > **[Glossary](/help/glossary)** > > For definitions of terms used in this FAQ. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.