Sanding our assholes with 150 grit.

Yet another reason why Informatica sucks

Something that took me 2 hours to develop in PL/SQL and takes less than a second to run took me 2 days to redo and takes 5 minutes to run.

It's not only the stupid pictures and mouse work that cramps my arm, it's that the only looping mechanism is in the batch equivalent workflows. Within a mapping, the code flows from left to right, only.

Why, why, why?
Permalink Shylock 
January 24th, 2012 10:11pm
Boys!
Permalink Quant 
January 25th, 2012 2:09am
> Why, why, why?


Well, interesting question, why? 

Is it *easier* for stupid people to use? 

Is it *cheaper*?
Permalink line noise 
January 25th, 2012 7:35am
It is significantly harder to use than a normal text based programming language (interesting that you can output the code to an XML language file).

It is incredibly expensive.

It is sold by an amazing sales force.
Permalink Shylock 
January 25th, 2012 9:05am
Oh, that's one of those 'program-by-picture' thingies isn't it?

Yeah, it's always going to suck. What's worse is the work it produces is always going to suck too.

They try to make that stuff so idiots can program. I don't know if you could formulate a more misguided design goal.

It's like making a robot who could perform all the techniques involved in surgery, then letting an accountant do open heart surgery with it. Even worse, they turn around and force veterans to use the thing when they already have good manual technique and experience.
Permalink JoC 
January 25th, 2012 11:51pm
It does format conversions fairly well. If you have, say, mainframe files, MSSQL, Oracle, etc. all mixed together, it's pretty good at creating staging.

The workflow doesn't suck terribly.

But put your business logic in the mapping, you have a circuit diagram.
Permalink Shylock 
January 26th, 2012 6:01am

This topic is archived. No further replies will be accepted.

Other topics: January, 2012 Other topics: January, 2012 Recent topics Recent topics