ETL tool migration : Best Practices in Parallel Run

674 views Asked by At

I am new to ETL migration. I have worked with Talend, but not yet faced the task to migrate large ETL project from one tool to another(IBM Data Manager to Informatica PowerCenter or Informatica Developer).

I am looking to general guidlines for migrate jobs from one tool to another one, and of course for my specific case.

I will be more clear:

The Databases Sources and Targes will be the same, what I have to migrate is the ETL part itself.

The approach will be the parallel run as suggested at this blog :

Parallel Run

In my case I have not to migrate the all DWH instead only the ETL as the old software will become a legacy one and the new one is from another Vendor(luckly both of them can export XML ).

I am looking for the pratical approch for parallel run, indeed I am been suggested to copy the Sources and Targes Tables in the orginal Database schema, but it does not look to me the best way to go(even not pratical when a schema has many tables).

The DWH I am woking of course has several DBS instance in Oracle and some in SQL Server, a Test server and a Production one, as well as for each, a Staging, Storage and a Data Mart area.

As from this related question and its answer, I am thinking to copy each schema on the go for each project.

Staging in ETL: Best Practices

Looking to have guidlines references, but my specific case is the migration from IBM Data Manager to Informatica PowerCenter

1

There are 1 answers

1
E LaRoche On

The approach depends on various criteria and personal preferences. Either way you will need to either duplicate parts or all of the source and destination systems. On one extreme you can use two instances of the entire system. If you have complex upstream processes that are part of the test, or you have massive numbers of tables and processes, and you have the bandwidth and resources to duplicate your system then this approach may be optimal.

At the other extreme, if any complex processes occur within the ETL tool itself, or you are simply loading tables and need to check they are loaded correctly, then making copies of the tables and pointing your new or old tool to the table copies may be the way to go. This method is very simple and easy to setup.

Keep in mind this forum is not meant to replace blogs and in-depth tech articles on those techniques.