dynamically change the database type in database connection
Hi everyone,
I would like to know if it is possible to switch database type
my source data comes from different databases like oracle ,SQL Server etc.
The way I tried implementing is by creation 2 dbconnections (one for SQL Server and the other for Oracle and gave the same SharedDbConnection Name) and the job can reuse that connection, add 2 tDbInputs for each database type and load the data into a buffer.
And do whatever I want on the buffer data, But the problem is I can't seem to reuse the connection in joblet in the job.
So im not sure how to handle this.
The only other way is to create separate child jobs for each source.
I did read through the below post, but I'm not sure if this could be applied to my situation
In the original post, they are using same DB but different connections based on the target table. But in your use case, your target DB itself is changing. When the DB is changing, there are lot of changes happening under the hood like changing the jar files and other associated code.
So my view is to handle them separately so that we will be able to track. Another flip point is that, we are trying to do lot of hand coding within ETL and maintenance will become difficult over a period of time. If you are planning to use governance layer on top of the jobs, the job crawlers will have tough time to handle these scenarios. They will not be able to track the end to end flow, which means more impact analysis time down the line.
In short, we may save some time in coding now but if we add up the total maintenance time for next 2 years, it will be more than simple execution process.
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved
In the original post, they are using same DB but different connections based on the target table. But in your use case, your target DB itself is changing. When the DB is changing, there are lot of changes happening under the hood like changing the jar files and other associated code.
So my view is to handle them separately so that we will be able to track. Another flip point is that, we are trying to do lot of hand coding within ETL and maintenance will become difficult over a period of time. If you are planning to use governance layer on top of the jobs, the job crawlers will have tough time to handle these scenarios. They will not be able to track the end to end flow, which means more impact analysis time down the line.
In short, we may save some time in coding now but if we add up the total maintenance time for next 2 years, it will be more than simple execution process.
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved
