Pentaho data integration community edition

#Pentaho data integration community edition free
#Pentaho data integration community edition windows

Want to write to three files at once? No problemo. most output support parallelism out of the box.In SSIS, you have to set-up a for each loop container, configure expressions, use variables. You just specify a folder, the metadata and youвЂ™re good to go, PDI will read all the files and append them to the output. some source transformations (like reading an Excel workbook or flat file) support reading more than one file at once.Want them? Write a custom component, use a 3rd party component or use a script task/component. most of them support regular expressions.Most transformations in PDI are also a bit more powerful than their SSIS counterparts: You also have a вЂњcalculatorвЂќ and a вЂњformulaвЂќ transformation that help you creating expressions. Lots of basic transformations you would probably do in SSIS with a derived column, are available in PDI as out-of-the-box components. Side note, just because you can create complex flows in SSIS, doesnвЂ™t mean you have to. Most of the time, I have to make another job just to make sure something doesnвЂ™t run in parallel when it doesnвЂ™t need to. In PDI, I find it much harder to organize dependencies. However, in my opinion, the control flow in SSIS makes it a bit easier for orchestrating complex flows: you have precedence constraints which you can assign OR and AND logic to you have containers for grouping logical units together. PDI has jobs for handling tasks and transformations for handling data (both are separate objects). In SSIS, you have to delete the precedence constraint, add the task and create two new precedence constraints.Д«oth tools have a similar structure: SSIS has a control flow for executing tasks and a data flow for transforming data in-memory, all in the same package. A very cool feature is that you can drop a transformation on an arrow between two existing transformations and the new transformation is inserted right between the two. PDI looks quite nice and most components are easily configured. SSIS has some clunky UI features which havenвЂ™t been updated since 2005: the notepad editors for SQL statements, the one-line editor for the derived column.

#Pentaho data integration community edition windows

SSIS on the other hand can only be developed on a Windows machine, but it can run on Windows and on Linux (since the latest versions).

But then again, itвЂ™s Java (owned by Oracle, you know what IвЂ™m saying). Because itвЂ™s Java, it can run on any platform (PDI seems to be very popular with the Linux crowd). Again, that can be seen as an advantage and a disadvantage.

PDI is a tool on its own, written in Java. SSIS is designed in Visual Studio (SQL Server Data Tools), which can be viewed as an advantage and a disadvantage at the same time. Both have boxes and arrows, sort of speak. User InterfaceД«oth tools are graphical ETL designers. IвЂ™m writing this blog post just to inform people and it might be of some assistance when selecting an ETL tool. IвЂ™m just stating observations IвЂ™ve done from working with both tools (although PDI for a much shorter time). It is certainly not my intention to say that one tool is better than the other. In this blog post, IвЂ™ll draw a quick comparison between both ETL tools.

#Pentaho data integration community edition free

YouвЂ™ve got an Enterprise edition (which ainвЂ™t free of course), but also a free open-source community edition (which is probably why kettle is known as an open-source ETL tool). PDI is the ETL tool of the Pentaho suite and is maybe most commonly known as kettle. IвЂ™ve been working with SSIS for a decade now (all versions, 2005 right until 2017), but itвЂ™s been just until recently that I got my hands on Pentaho Data Integration (PDI).