topic Re: Connecting to SAP HANA - limit tables in Administration and Deployment

Connecting to SAP HANA - limit tables

Filipvdr — Wed, 07 Oct 2020 07:43:47 GMT

Hello,

I'm able to connect to our SAP HANA server with the libname:

LIBNAME HANA_LD SASIOHNA  PRESERVE_TAB_NAMES=YES  SERVER="a61db.al.ndis.be"  SCHEMA=_SYS_BIC  USER=TST003  password="Test123$";

It works, but i want to hide the tables with "/hier/" from the library. Are there any options i can pass in the libname to do this?

Thanks.

Re: Connecting to SAP HANA - limit tables

SASKiwi — Fri, 09 Oct 2020 02:26:31 GMT

If you are OK with setting up the library in SAS metadata you could just register the non-hier tables so those would be the only ones that showed. However using a LIBNAME statement would bypass this.

Discuss your issue with your SAP DBA as they could probably setup a special schema that hides these.

Re: Connecting to SAP HANA - limit tables

Filipvdr — Fri, 09 Oct 2020 07:29:34 GMT

The goal is that every single user will connect from SAS Eguide to SAP HANA with his own user so we will have to set security only at the SAP HANA platform.

So registering the library in metadata would mean we would have to do it for every user, and update (new) tables regularly.

Is it possible to create a metadata library which uses something like &metapassword?

Re: Connecting to SAP HANA - limit tables

SASKiwi — Fri, 09 Oct 2020 21:53:01 GMT

@Filipvdr - A library set up in SAS metadata only needs to be defined once and then shared with all EG users. If SAP HANA can authenticate against OS user accounts that would be ideal as you don't need to supply a user and password any more. An alternative would be to use token-based authentication where all SAP HANA libraries share the same user account for connection purposes.