How to create a .hdbvirtualtableconfig file for remote source and schema name change

[former_member590265]

Hi Team,

I am working on the HANA XSA project. In our project I have a requirement to access the cross container data. My source and target containers are located in the different tenants. So I am using SDA remote source and virtual tables between 2 tenants to access the data between the containers. Our development space and production spaces are located in different tenants.

In development spaces I have used SDA remote source connection 'ABC' and schema 'TEST_SCHEMA_1' in the .hdbvirtualtable file to create the virtual table. This virtual table in development space is working fine. But now I am facing problem in production space where SDA remote source connection name is changed to 'XYZ' and schema name is changed to 'TEST_SCHEMA'. In .hdbvirtualtableconfig file how I can configure these 2 changes so that my virtual tables in production space will created with SDA remote source connection 'XYZ' and schema 'TEST_SCHEMA'. As I know we cannot edit or create virtual tables in production space and now the only way .hdbvirtualtableconfig file. But I am not able to find any document or help on how to create .hdbvirtualtableconfig file which will include remote source connection name and schema name change in production space.

Thanks in advance.

BR,

Vivek.

[SreekanthSurampally]

yes, I understood your requirement, I never worked on requirement to access objects in one tenant-space to other tenant-space in a same database.

But my point is , creating a remote source connection on hdi container in developer sapce leads to confusion because, when this space is enabled for development, there will be multiple schemas created, like TEST_SCHEMA_1, TEST_SCHEMA2 etc..for each developer. Also, the table you are referring is going to be available in all those schema, so how can you make sure TEST_SCHEMA_1 is to be used as the source of remote source? Secondly, if you can have remote source name same in 2 places in Dev spaces, then deployment of that into prod space will work fine.. is that possible?

if this is not making sense, I may be wrong. Then we will wait for experts Florian, thomas.jung, rich.heilman to reply on this.

[former_member590265]

Hi Shreekanth,

To answer your first question; we have agreed in project to always use TEST_SCHEMA_1 for the virtual table creation in the development space.

Second question; If we keep the same remote source name this problem may solve for remote source name but I still have problem with database name and schema name. Other problem is basis team following naming conventions for remote source creation and they use the source and target tenant names in that. Its difficult to convince them to keep it same in production also.

Thanks.

Vivek.