if you’re like me, you work in many many environments. i’ve been a long-time user of powercenter and informatica’s products continue to shine for me. i can develop stuff in informatica very very fast. i’ve recently (over the last month or two) gotten really good at building owb mappings, and while i kind of like the 100% push-down end-result (oracle packages are produced), i am weary of working in the designer. there are so many design time quirks and bugs that it’s hard to “get motivated” to create inside owb designer. i’ve recently heard that oracle plans to “replace” owb/omb with something new, something they just acquired… we’ll see what happens. this entry is very short, and compares designining mappings in owb versus informatica powercenter.
i use design patterns to actually design the same functional mappings in both environments. highly restartable, fault-tolerant, parallel enabled, performance driven, etc… to that end i spent some time in owb designer building the mappings that i have built in powercenter in the past.
here’s the sunopsis (sorry for the pun ie: synopsis) of it all…
45 minutes to design, debug, and deploy a mapping with de-dup, expression (datatype re-cast), lookup, filter, constant, sequence generator, and target.
10 minutes for the same thing, that’s a huge savings, but wait theres more!!
an additional 15 to 25 minutes was spent adding and moving fields around, realizing that i had to add a data type cast expression myself, and that the deisgn tool wouldn’t do it for me, which ended up in 1 corrupted mapping, another edition of the mapping (re-written by hand + another 20 minutes) wouldn’t synchronize the lookup properly, so yet another re-write by hand (this time 20 minutes on top of it all)… and finally i had a mapping that validated.
once it validated, it wouldn’t deploy properly – when i deployed i got oracle “parenthesis” and other obtuse errors – when i examined the deployed code, there was nothing wrong with it, but i was pointed to “conditions” in the lookup, and the filter. i had to go back to the lookup & filter, and manually validate each of these by pressing the validate function. once validated, it deployed – no errors.
so, 1.5 hours later i had a working mapping. with informatica, added a session and a workflow, and a total time of 15 minutes, and it was running.
take your pick…. i’d say design time in owb is slow slow slow…
by the way – what have you found? love to hear your numbers and feedback, add a comment below…
what about the fun side of the island? (sorry, quip from the movie: madagascar)…
the fun side of the island is… tada! code generation…. i can now generate etl code for importing to owb, and importing to informatica. total result? i can import flawless 100% ready-to-run code for both tools in record time.
in other words, i’m not stuck on the designer in either tool anymore… i can generate code from a cross-reference, a source, and a target model for all hubs, all links, and all satellites – over 150 mappings in less than 20 seconds, and i can choose: run them in owb or run them in informatica (makes no difference to me).
you can contact me for more information on this, i’m thinking of releasing this feature set as saas – let me know if you are interested.