Yuri Abele;
I as at fan SQL have one question
- That forces to write transformation in the graphic tool, instead of what to use SQL (PL-SQL/T-SQL/etc)?
1. Transformation no means always works with one data source. For example I wrote on PDI comparing of the data from MySql and Oracle, i.e. already, at least, two different on different bases and an output of differences to the report. (About ODBC and other Win-pribludy it is not necessary - all under )
2. At spelling SQL to be mistaken somewhere in small things easier (type, save-pastes brought, in line a position overshot, etc.), and here all elements already and work.
3. The ready mechanism of debugging, testing, layout of each step on runtime etc.
4. Pentaho consists not only from PDI, and of a tooling. I.e. you write transformation, then you put it on job/cron in Pentaho Analytics, and any other transformation you pull from Pentaho Report which, in turn, too thrust in Pentaho Analytics.
5. Draw pictures the person who is not strong in SQL can.
Well etc. and .
- why eTl instead of elT?
Tasks different happen.
