Skip to Content

HANA DB: Multiple Schema Sharing Same DB objects

Hi All,

We are pretty new to HANA DB. We have a scenario where our main web application is maintaining multiple data bases (currently in SQL Server) corresponding to each client. The DB objects (tables, stored procedures etc) are the same across all data bases, hence currently only one version of these objects needs to be maintained. We are switching to HANA now and planning to retain the same approach of one schema per client. However, the issue we are facing is maintaining the DB objects. Since HANA has schema name appended to each DB object, we will end up having one version corresponding to each client.

1. What is the best approach in this scenario, so that we dont have to maintain 'n' versions of DB objects?

2. Several blogs mentions that it is recommended to maintain separate schema for SLT replicated tables and BODS replicated tables. Why is this necessary? What is the downside if we maintain all tables in one schema?

Thank you,

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Mar 25 at 05:41 PM

    My two cents:

    1. What is the best approach in this scenario, so that we dont have to maintain 'n' versions of DB objects? --- I don't think so. You can use the SAME physical table in one schema. For your "client specific schemas", you can create those schemas and create database views mapped to the physical table in the earlier schema. Again, this is very generic and simplified answer. There are some more possibilities and options depending upon the detailed requirements.

    2. Several blogs mentions that it is recommended to maintain separate schema for SLT replicated tables and BODS replicated tables. Why is this necessary? What is the downside if we maintain all tables in one schema? --- To my knowledge the SLT schema is created as part of the SLT implementation. Those objects are exact copy of the source data. BODS may be able to create tables in the same SLT schema, if you grant BODS user access to create objects in the same schema. But from the governance perspective, it is a good practice to keep those schemas separated. Again, it is your choice.

    Add comment
    10|10000 characters needed characters exceeded