Welcome to the SAP HANA Connector setup guide! This document serves as a comprehensive guide for configuring SAP HANA to integrate seamlessly with Savant using the below mentioned methods.
Features
Read data from SAP HANA
Requirements
Access to SAP HANA 2.0 SPS 03+ (MDC tenants supported) or
Access to SAP HANA Cloud (latest)
Ensure that Savant's IPs are whitelisted to reach the host/port.
Connection Methods
Savant supports the below method:
Database User (direct)
This step-by-step guide ensures you can efficiently set up your environment for optimal data integration.
Database User Method
Step 1: Setup Network Connection
Check the DNS or IP of your HANA host or HANA Cloud endpoint to get the Host/Server details
Use 4403 for HANA Cloud (secure SQL port). For on‑prem MDC, ports may follow the
3<instance_no>15pattern (e.g.,30015), but in most HANA Cloud environments the default is4403.Provide the CA/Server certificate if required by your environment to setup a SSH connection
SSH tunnel (optional): If HANA is not publicly reachable, enable an SSH jump host that can reach the database.
Step 2: Grant Permissions in SAP HANA
Create a read-only user with metadata visibility. Minimum privileges:
CATALOG READSELECTon target schemas/tables/viewsFor views referencing other schemas, ensure the user (or role) has
SELECTgrants to all underlying objects.
Optional (only if needed by your usage):
CREATE LOCAL TEMPORARY TABLEon user schema (for complex queries that need temp objects)
Recommended role pattern
Run as an administrator
CREATE ROLE SAVANT_READONLY;
GRANT CATALOG READ TO SAVANT_READONLY;
GRANT SELECT ON SCHEMA <YOUR_SCHEMA> TO SAVANT_READONLY;
Repeat the SELECT grant for each schema you wish to expose
CREATE USER SAVANT_USER PASSWORD "<STRONG_PASSWORD>" NO FORCE_FIRST_PASSWORD_CHANGE;
GRANT SAVANT_READONLY TO SAVANT_USER;
Optional: restrict to a tenant DB, set default schema if desired
ALTER USER SAVANT_USER DEFAULT SCHEMA <YOUR_SCHEMA>;
Step 3: Configure the connector in Savant
In Savant, go to Connections → Add System → SAP HANA.
You’ll see the following fields (matching the UI):
Server*: HANA host or endpoint (e.g.,
hana.mycorp.localor<tenant>.hana.prod-eu10.hanacloud.ondemand.com)Port: For HANA Cloud, use 4403. For on‑prem, use the appropriate SQL port.
Database: (Optional) Tenant database name or use H00
Username*: Database user (e.g.,
SAVANT_USER)Password*: The user’s password
Use SSL/TLS (Optional): Check to enforce encrypted connection
SSH tunnel(Optional): Check if you must connect through a bastion (then provide SSH details)
Click Authenticate. On success, Savant will validate schema access and list available objects.
Troubleshooting
Authentication failed or invalid credentials → Verify username/password, account lock status, and tenant target; in MDC confirm connection to correct tenant.
Cannot connect or timeout → Check that Savant IP is allowlisted, confirm host/port (4403 for HANA Cloud), and ensure firewalls permit traffic; if using SSH, verify bastion access and credentials.
TLS/SSL errors → Ensure certificate CN/SAN matches hostname or update certs, and upload CA chain in Savant if private CA not trusted.
Insufficient privilege → Grant
SELECTon all required schemas/tables/views and addCATALOG READfor metadata discovery.Object not found or invalid schema → Use fully‑qualified names (
SCHEMA.TABLE) and confirm or set default schema.