Hi HANA-experts,
I am new to HANA development so I hope I'm asking this in the right forum as I am investigating multi-tenancy features. Our enterprise application itself is a multi-tenant application (meaning we service many customers in a single system, and we support more complex hierarchies of tenants (e.g. parent companies etc.)). Right now it is implemented by having 'tenant FKs' in each table. The problem, I think, with this approach is that as we'll be migrating many of our customers data into this single-catalog we can't make snapshots (for rollback) on a per customer basis, meaning we can't roll back using database-features and are left to implement such functionality in the application.
HANA's multi-tenant containers, if I understand correctly, however would allow us to partition each customers data, by moving each into its own schema/catalog, but then we lose abilities to do any other queries but SELECT DML. It seems from your online material a tenant from the perspective of HANA would therefore not be a customer in our enterprise system but rather the enterprise application itself, is this a correct conclusion?
What is the recommended strategy for dealing with such applications? what options do we have to achieve multi-customer-tenancy without reinventing the wheel? would partitioning per customer be a solution? Is it possible to keep data isolated yet have it available in the same schema?
Best regards,
Aias