The HANA Licensing Landscape for Multi-Tenant Environments
A common query among HANA administrators is how system-wide and tenant-specific licenses interact in multi-tenant setups. Let’s delve into the intricacies of HANA licensing to clarify these aspects.
Read also – Reclaim HANA Log to avoid log full situation.
Scenario: A 750 GB HANA system hosts two tenants, A and B, without dedicated tenant licenses.
Question 1: Shared or Individual Memory Limit?
The 750 GB license applies to the entire HANA system, not individually to each tenant. This means the combined memory usage of all tenants must remain within this limit. Adding a third tenant, C, will further constrain the available memory for each.
Question 2: Tenant-Specific Memory Quotas?
While you can set memory quotas for individual tenant databases, these quotas are not enforced directly by the license. They are system configurations that help manage resource allocation. However, the total system memory usage must still adhere to the 750 GB limit.
Question 3: Impact of Tenant-Specific Licenses?
Acquiring a 1.5 TB tenant-specific license for Tenant B does not automatically increase the system-wide capacity. It grants Tenant B the potential to use up to 1.5 TB, but the overall system remains restricted to 750 GB unless the system-wide license is upgraded.
Key Takeaways:
* The system-wide license acts as a global cap on memory usage across all tenants.
* Tenant-specific licenses allow individual tenants to consume more memory, but the total system capacity is still governed by the system-wide license.
* To increase the overall system memory capacity, you must upgrade the system-wide license.
By understanding these principles, HANA administrators can effectively manage resource allocation and ensure compliance with licensing terms in multi-tenant environments.