Posted by dba_222 on 04/19/07 15:13

OK. But I still have questions.


Is it because there are 3000 built in functions
and commands specific to the ETL tool, and a number
of new paradigms, that you first have to master?
Since I don't see big thick books on the tools,
if any, I don't believe this is the case.


Or, is it that the new esoteric mappings themselves are
difficult? They always are. In which case, I conclude
that it doesn't really matter whether you use an ETL tool, or
hard code it, the mappings will be difficult either way.

Actually, I can imagine that an ETL tool may actually
slow you down, because it's more limited in functionality
than hard coding. In which case, I can understand that
you will need to spend time with the tool, trying to
get it to do the things that it wasn't designed to do.
Is this the case?

The idea that I'm getting at is transferable skill sets.
If someone knows C++, they can learn java much easier
than one without the OO knowledge. If one knows databases
and SQL in depth, and can hard code ETL, this is also
a transferable skill set.



Again, Questions:
- Just how difficult are these ETL tools to learn
for an experienced Oracle pro like myself?

- Other than a GUI, making everything simple to use,
just what are the advantages of using ETL tools?

- what built in functionality do ETL tools
have, that can't be done in PLSQL?

[Back to original message]