Regarding Access based display in modeling views in SAP HANA Studio

[Former Member]

Hi,

I have a query: Is there any way that I can filter out the selection of tables in data foundation based on my access and authorization?

It's required for my case as there are several users working on HANA single instance simultaneously and each one of them may create some or other tables (of course under same user but in different namespace etc.) for which I am not authorized to access so I end up checking among lots of tables.

Is there any quick way of handling the same?

Thanks,

Rachit Kumar Rastogi

[lbreddemann · Accepted solution]

So in short you want to have a partly shared and a partly private schema and the database should provide the means to figure out when to use which.

There is no technical feature to support this (actually I don't know any DBMS that would have something like this).

Generally speaking, the schema of a SQL database is rather static and cannot be determined based on a session. Sure, you might re-direct data access e.g. via views and synonyms, but object compilation resolves those upon compile time.If the structure changes afterwards, the objects and queries will become invalid.

Your question actually states how to implement your solution to the problem, rather then the problem itself. Maybe there is something we can propose when you share what you actually want to achieve.

[Former Member · Accepted solution]

Hi Lars,

Thank you for reply.

Yes, it's correct once the data is pulled from DB it's static and can't be filtered out based upon user login session before fetch.

However my query is that there shall be an additional button or selection option to filter out the "fetched results" with tables that I can access.

So is it possible that I can filter out the result one level further from table selection screen itself?

Best Regards,

Rachit Kumar Rastogi

[lbreddemann · Accepted solution]

Ok, you're mixing requirements here.

First you were talking about a dynamic data model, that changes according to the user.

Now you want to have the list of tables that are available to modellers to be limited. This is fairly straight forward as the modellers only see tables they have access to anyway.

Except of course, you have provided them with a system privilege like CATALOG READ.

Anyhow, you should be aware that HANA Studio is a development and admin tool - it's not meant for end-users.

If you want to restrict what your developers can see: roles are the way to go here.

[Former Member · Accepted solution]

Thank you Lars!