Feb 10, 2014

ETL Application Comparison, Part 7

With this post we are concluding the ETL Application Comparison series. In order to provide an overview of the different applications we have looked at, I have composed a table listing the most significant strengths and weaknesses of each tool. I hope that you have found the series insightful, and that it has helped to create a better idea of the software that is available for building automated ETL processes.
Strengths Weaknesses

PDI 5.0.1

  • Provides steps for quickly doing simple, common things, as well as steps for handling more advanced tasks
  • Agile flow of data rows
  • Step Metrics provide insight into the performance of the constituent steps in transformations
  • Cross-platform
  • Most text fields do not support expressions, forcing the user to introduce additional steps for making calculations
  • Offers no background-running process for facilitating scheduling or monitoring

Linx 5.0 Beta

  • Features a minimal set of versatile, but simple components
  • Widespread use of C# expressions
  • Visual editor provides a concise view of the process
  • Simple and clean way of scheduling and monitoring processes
  • The current beta version offers no component for writing custom C# code


  • Offers some powerful components like the Script Component
  • Very developer-oriented; not so user-friendly

Jaspersoft ETL 5.2

  • Java code view offers transparency
  • Widespread use of Java expressions
  • Cross-platform
  • No expression editor
  • Flow of data rows between components is rigid
  • Frustrating experience for new users not familiar with all the quirks

AutoMate 9

  • Widespread use of BASIC expressions
  • Good expression editor
  • Easy to create and manage schedules
  • Program’s representation in the visual editor is overly verbose and long-winded
  • Runs slow for ETL tasks

No comments:

Post a Comment