From 6ad657797477dac696e69422d14363c8f7e43d75 Mon Sep 17 00:00:00 2001 From: Eckart Liemke Date: Mon, 4 May 2026 10:25:57 +0200 Subject: [PATCH 1/3] admin plan warning --- guides/multitenancy/index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/guides/multitenancy/index.md b/guides/multitenancy/index.md index 5d0bbb6c14..e49f7bafc2 100644 --- a/guides/multitenancy/index.md +++ b/guides/multitenancy/index.md @@ -832,6 +832,11 @@ If you start with a multitenant application that's configured to use to SAP HANA service: hana-cloud service-plan: hana-multitenancy ``` + +> [!danger] Do NOT use the hana-multitenancy-admin plan +> The tenant containers are filtered by the hana-cloud service instance. When using the `hana-multitenancy-admin` plan, +> applications will potentially access data of other applications. + For SAP HANA TMS v2, you also need to specify the database ID of the database that you plan to use for your tenant containers. You can specify this using the [`cds.xt.DeploymentService` configuration](/@external/guides/multitenancy/mtxs#deployment-config). To keep the application configuration agnostic, we recommend adding the cds/requires/cds.xt.DeploymentService/hdi/create/database_id configuration as an environment variable to the MTX service in _mta.yaml_: From f3549b4ef7a7e11be22a3102f24d80cfa9f561cd Mon Sep 17 00:00:00 2001 From: Eckart Liemke Date: Mon, 4 May 2026 10:42:38 +0200 Subject: [PATCH 2/3] avoid to mention the wrong plan --- guides/multitenancy/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/multitenancy/index.md b/guides/multitenancy/index.md index e49f7bafc2..615621416c 100644 --- a/guides/multitenancy/index.md +++ b/guides/multitenancy/index.md @@ -833,8 +833,8 @@ If you start with a multitenant application that's configured to use to SAP HANA service-plan: hana-multitenancy ``` -> [!danger] Do NOT use the hana-multitenancy-admin plan -> The tenant containers are filtered by the hana-cloud service instance. When using the `hana-multitenancy-admin` plan, +> [!danger] Only use the hana-multitenancy plan +> The tenant containers are filtered by the hana-cloud service instance. When using a different plan, > applications will potentially access data of other applications. For SAP HANA TMS v2, you also need to specify the database ID of the database that you plan to use for your tenant containers. You can specify this using the [`cds.xt.DeploymentService` configuration](/@external/guides/multitenancy/mtxs#deployment-config). From 343a7525b1be2d1af5cd709b1f749da268a2a815 Mon Sep 17 00:00:00 2001 From: ecklie <52252271+ecklie@users.noreply.github.com> Date: Mon, 4 May 2026 13:21:14 +0200 Subject: [PATCH 3/3] Update guides/multitenancy/index.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: René Jeglinsky --- guides/multitenancy/index.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/guides/multitenancy/index.md b/guides/multitenancy/index.md index 615621416c..6994ab476c 100644 --- a/guides/multitenancy/index.md +++ b/guides/multitenancy/index.md @@ -833,9 +833,8 @@ If you start with a multitenant application that's configured to use to SAP HANA service-plan: hana-multitenancy ``` -> [!danger] Only use the hana-multitenancy plan -> The tenant containers are filtered by the hana-cloud service instance. When using a different plan, -> applications will potentially access data of other applications. +> [!danger] Only use the `hana-multitenancy` plan +> As the tenant containers are filtered by the SAP HANA Cloud service instance, applications will potentially access data of other applications when using a different plan. For SAP HANA TMS v2, you also need to specify the database ID of the database that you plan to use for your tenant containers. You can specify this using the [`cds.xt.DeploymentService` configuration](/@external/guides/multitenancy/mtxs#deployment-config).