How to develop a project when only a Talend Remote Engine has access to a database, not the Talend Studio?

[Anonymous]

Hello everyone!

I have a Talend Cloud licence (Remote Engine included)

I have to develop jobs that will request databases (Microsoft SQLServer) that are accessible only in a private network.

My Talend Studio is on my PC and not in the private network (no access to database)

My Talend Remote Engine is in the private network (with access to database + access to internet)

I can the access the Talend Remote Engine's Server by RDP (Remote Desktop Protocol). Therefore I can access to the databases to get the table schemas manually.

My Talend Studio cannot get database table schemas automatically, (which is a pain because have to work with a lot of tables).

Is there an easier way to get table schemas than the manual way ?

I thank you

[fdenis]

I saw tree way.
you can deploy a job who export system tables (view on Objects).
you can ask t the db owner to have db scropts.
you can Install a studio into private network to get connection and tables structures.

But the best way is to have a full développement environnement.
The good question is how are they going to validate your job bifore production?

they need dev and uat environments

[Anonymous]

The third one seems to be the more confortable by far! If I understand it well it is like having a full developpement environnement.

With installing a Talend Studio in the private network (of my client), the thing is : 1- I know my client would prefer to not to have allocate hardware for it. 2- I am not sure its the only confortable way to developp.

By creating this discussion, I am listening to the community before insisting more on my client on allowing me to use a Studio in the private network, in case there is a solution i didn't know.
So I thank you for your answer

To answer your question: I have to Remote Engine (DEV for validating + PROD) which seems ok to me

[David_Beaty · Accepted solution]

Hi,

As you mention, this is SQL Server - you can get the database created with all associated tables, indexes, views etc, somewhere locally (SQL Server Express on your local studio PC). No data would be involved, but it would be the database & all table schemas.

This will also help you develop, away from the production site.

[Anonymous]

Hello David,

I thank you for your answer!

This is a quite nice solution.

In my case, the database schemas are still evolving since they are part of a project. So in my case, I should often ask for database dump. But finally, this is still a very interesting alternative which I will consider.

I will let the discussion unsolved for a few days just in case there were a "perfect solution". But I think that you David and Denis already have brought quite nice alternatives.