I work for a young medium sized enterprise which is currently
busy in several migration projects as a consequence of
for example streamlining workflow processes, development of
new applications as replacement for existing legacy applications,
implementation of reporting solutions.
Given these general points where would a solution like Pentaho
come into play?
I worked in a medium-large enterprise (a bank) which required regular integration and transfer of data from a variety of sources, including 2-3 brands of database, 2 separate IBM mainframes, the occasional spreadsheet and probably a few other things I've tried to forget. Kettle is great for that kind of stuff.
In the larger BI suite, the Pentaho report designer is good for constructing reports for Java webapps - either the BI server or external applications. We didn't use Pentaho for's OLAP capabilities, but that's because we weren't aware of them at the time.
One thing that's great about the Pentaho tools is that their control files are all XML format. Back then we were using the Microsoft DI tool, and it was frankly, hopeless. It was intended to be set up tediously and manually via a GUI interface. You could dump it to a really long and ugly Visual Basic format, but that was about it. Maybe do some OLE control, but not from our Sun servers, of course.
It's not infrequent, however, for me to make batch updates to Pentaho control files, however. In fact, just yesterday I took a whole raft of transformations and ran them through sed to add stuff that wasn't worth manually doing when I designed each transformation. For more extensive mods, I use XSLT. One of my favorite tricks is to take a Jasper report definition and do wholesale tweaking of the fonts on a page just to see what looks best. You can't do that with products such as (pick-a-random-IBM-product) which use binary file formats.
Customer surveys are for companies who didn't pay proper attention to begin with.
Confirm with Tim, I work in a medium healthcare focused business, and same lines as Tim multiple database types, Excel file input/output (which Pentaho Reporting has a HUGE advantage - multi-tab excel reports based on grouping that business people love).
Database Migrations, i.e. swapping from say MS SQL 2000 to 2005 (to 2008), using the JDBC drivers, are relatively low-worries - DTS jobs I get sketched out swapping database versions while Pentaho not so much.
I think Tim mentioned more experience with Mainframes than I, but I do know Pentaho Data Integration has several file formats (including IBM500) to support loading of some of those obscure character sets.
I agree with Darren and Tim. Pentaho is well suited for companies of all sizes. In particular, Kettle has nothing to envy the commercial ETL tools. Kettle is perfect for ETL processes of all kinds and dimensions,