![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Any links, pointers, studies? |
#3
| |||
| |||
|
|
"Wolfgang Keller" <wk (AT) objectarchitects (DOT) de> schrieb im Newsbeitrag news:ae01a906.0312081042.6f24cb60 (AT) posting (DOT) google.com... |
|
I doubt that you will find more than success stories and generic hints on how ETL tools can increase productivity. You will most probably find the first on the Web pages of the ETL vendors. |
#4
| |||
| |||
|
|
"Joerg Narr" <n_o_spa_mjoerg_narr (AT) hotmail (DOT) com> wrote "Wolfgang Keller" <wk (AT) objectarchitects (DOT) de> schrieb im Newsbeitrag news:ae01a906.0312081042.6f24cb60 (AT) posting (DOT) google.com... Joerg, I doubt that you will find more than success stories and generic hints on how ETL tools can increase productivity. You will most probably find the first on the Web pages of the ETL vendors. thanks! Your answer is in line with what I heard from a metrics guru He had never seen a piece on ETL productivity passing over his desk .. Seems I can stop searching Thanks anyway Wolfgang PS: HEY ACADEMICS - here's a potential Ph.D. theme .. it's free, it's interesting and nobody has done it yet :-) |
#5
| |||
| |||
|
|
You must be kidding. ETL is one of the most ridiculous pieces of software that adds absolutely no value to your data; quantitatively ZERO. All an ETL tool does is converting operational data so that it can be fed into else where. Why didn't some one engineer in the first place that 'else where' to be good enough to take operational data as it is? ETL is just a work around of poorly engineered artifacts and in your opinion it 'increases productivity"? |
![]() |
| Thread Tools | |
| Display Modes | |
| |