Please can anyone advise if it is a fine practice to have multiple schemas in HANA :
- Schema 1: Accounts Payables
-Schema 2: General Ledger
- Schema 3: Account Receivables
At present we need ability to classify RUNTIME Catalog objects like TABLES and Stored Procedures under its Schema
Doing this, does it have any performance issues or limitation on Security and Privileges etc ?
I may be able to partially answer your question.
Yes, indeed, you may be able to have multiple schemas. Depending on how the security of your business needs to separate data it may go into different tables (maybe not necessarily different schemas).
You can also have tables/stored procedures as design time objects so that it facilities the migration between environments or if you already have runtime objects then it is not a problem.
Further, the security / privileges, the more schemas you have, the more roles/privileges you will need to maintain, which may not be bad but just be aware of the maintenance involved to have such structure.
others may be able to add to this answer. hope I was able to provide some knowledge
In HANA instance, schemas generally represent the source systems (ECC, BW, Flatfile..) and also there will be a schema created for each Database User in HANA.
To classify the modeling content (views, tables, procedures etc..), we have to use the Packages.
Since packages are also used to group the objects, that can be transported together, they are the ideal for classification of objects. Also you can maintain the hierarchy of packages as per your classification needs.
For example: Project_name.Finance.AP
Hope that helps..