SAP Hana Catalog user Managment (Strategy)

[former_member376663]

We have a Project where we leverage HANA reporting capabilities and developed Calculation views , Catalog views on top of the catalog tables .
These tables and Catalog views were initially created by "SYSTEM" ID and that worked well until now . Now the Audit has mandated us to no longer use
SYSTEM ID . Now if we create a view using any other ID , view gets created but End users are not able to access that view . What we understood from the issue
is that both view and table should have the same owner to properly propogate the access when a view is accessed .

Here is how you can recreate issue what we are having:

1.Create Table T1 using SYSTEM id or USERID1
2.Create View V1 using table T1 using different ID: USERID2
3.Ask USERID3 to execute View V1. It will get authorization error.

Question is what is industry standard practice on managing Catalog objects Tables, Views etc. which is sustainable solution in long term ? How other companies are managing their Catalog objects, using which ID ? and How ?

[lbreddemann]

The manageable, sustainable approach is to not use catalog tables.

The privilege, access and ownership issues you experience now are just three reasons for that.

Beyond that, repository objects can be developed and deployed more safely with fewer things to worry about.

My recommendation for your situation would be:

• re-model the schema, tables, and views as repository objects
• create repository roles and analytic privileges (if used)
• load the data from your current tables into the new tables
• bind your client tools to the new, activated runtime objects

That will take you a bit longer than the manual recreation but will get rid of the problems you have altogether.

All this is of course explained and documented in the SAP HANA Developer Guides. That's the "industry standard" you want to follow.

[former_member376663]

Lars,

Thank you for your answer. We do use repository objects in most cases, however there have been situation where our modeler had to use Catalog objects on certain views where we needed right strategy to manage catalog objects correctly. Hoping someone can answer it correctly.