Database Connections & Inputs - Best Practices

Six Stars

Database Connections & Inputs - Best Practices

I have a Job that needs to read 12 different tables from the same MSSQL database.

Is it better to use 1 tMSSqlConnection and set all 12 tMSSqlInput to "Use Existing Connection"?  Or is it better to keep the database parameters local to each tMSSqlInput?

Thank you in advance!

Forteen Stars

Re: Database Connections & Inputs - Best Practices

it depend from You Job logic
generally more easy define single connection and close it after finish Job
with single connection You are as well can enable auto commit or use manual/rollback commit when it needed
but at the same time - all Your tables must be in same database(schema)

without single connection:
You can manage commit windows (commit every XXX rows)
You can have separate Database(schema) for each Input component

From information point of view:
if You use context variables instead of hardcoded details - change any information will be same, in single place only
-----------

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema

Blog

Best Practices for Using Context Variables with Talend – Part 4

Pick up some tips and tricks with Context Variables

Blog