Efficient ways to shared SAP HANA Cloud HANA Database amongst DEV, QA and PROD subaccounts in BTP

[nilayghosh]

Hi all,

For a customer project, I am using BTP ABAP Environment to develop a few data intensive custom applications which will access the data residing in the SAP HANA Cloud, HANA Database. I have a subscription of SAP HANA Cloud, HANA Database.

If I want to share this subscription of SAP HANA Cloud, HANA Database amongst the DEV, QA and PROD of my BTP ABAP Environment, I want to know which of the following options are the most cost effective but capable of having the data separated between the DEV, QA and PROD environment:
1. Creating multiple instances of the HANA Database within the single SAP HANA Cloud subscription
2. Creating multiple tenants (as per the latest feature released in Q4, 2024) with HANA Database of the single SAP HANA Cloud subscription

Any guidance or first hand experience on this topic would be highly appreciated.

Thanks.

[Cocquerel]

Within my company, we are using the same HANA Cloud instance for DEV and QA.
All our HANA development are done use HDI (HANA Deployment Infrastructure).
It means the related MTAR files are deployed twice on the same instance: once for DEV and once for QA.
To avoid conflict of schema name, we are adding a suffix at the end of schema name for QA deployment. To be able to change schema name at deployment time, we are using an MTAR extension (.mtaext) in our CI/CD pipeline.
Note that on application layer (ABAP Cloud in your case), you have to use virtual schema name in your ABAP coding and have different mapping with physical schema name depending if your are on DEV or QA ABAP instance.

[nilayghosh]

Thanks for your response Cocquerel. Does it mean that you have one instance of SAP HANA Cloud HANA DB for DEV, QA and another one dedicated for PROD?

[Cocquerel]

Yes, for PROD, we prefered to have a separated instance. This way, we are able to test HANA Cloud upgrades first on non-prod before doing them on prod.