Rhino ETL opinions vs Kettle and SSIS

I am considering a tool for an ETL solution that has high daily demand and requires heavy business logic processing. I've tried kettle and SSIS so far, and also want to test for Rhino ETL. I don't care for the visual flow structure of both Kettle and SSIS and creating complex businesse rules seems really hard using them... Rhino ETL seems more friendly as it has its own DSL to transform the data and I can also use C#.

Finally, my question is: Anyone uses Rhino ETL heavily? It has good performance compared to Kettle and SSIS? How about maintainability?

Thanks

UPDATE:

In comparisons that I made between Kettle and SSIS, Kettle was, without a doubt, better. I am considering Rhino ETL for its pragmatic approach compared to Kettle. As said in the comments, it seems a step backwards, but the kind of validation needed isn't the kind of problem Kettle is recommended for. For example, one of our integrations receives some kind of schedules that must be validated against the existing ones in the system, they must not conflict, there are several types of schedule and the conflict validation rules are complex. The system already has an User Inteface to do it, and the business logic is already implemented in C# code. Any attempt to port it to Kettle seems incredibly difficult, besides, it violates the 'only one way to do a thing' principle.

The 'no one uses' problem adressed in the comments is a concern for me too, that's why I am here trying to find out if anyone uses it in heavy production environment.

Thanks for the feedback so far.

Why bother saying SSIS is horrible if you won't say why it's horrible? I happen to think you must be on drugs if you prefer the kind of hacks necessary in DTS to the clear control and data flow in SSIS.

John Saunders 2010-02-25 19:50:29

The objective is to be developer oriented, no DBA or admins interference at all... We look for robust maintainable ETL code, and both Kettle and SSIS seems to lack this...

Pedro 2010-02-25 20:02:28

@John do not compare simplicity with power. As for drugs check out this links or simply STFG on Microsoft Connect and Web.http://ayende.com/Wiki/I+Hate+SSIS.ashx http://ayende.com/Blog/archive/2006/01/12/SSISDebuggingFrustrations.aspx http://ayende.com/Blog/archive/2007/07/27/SSIS-The-backlash.aspx

Sergey Mirvoda 2010-02-25 20:49:40

@Pedro hm, our ETL goals not same as your goals, after rereading question I think you should check workflow engines.

Sergey Mirvoda 2010-02-25 20:54:16

@Sergey: the "drugs" comment was about liking DTS better. No drugs are required for simply disliking SSIS. I read those links, and Ayende should have got help (from Jamie Thompson, for instance), when he was learning SSIS. He raves like someone who tried to figure it out without the manual or any other help. The first five or six things he says are dead wrong. I gave up after that. Note he also doesn't say DTS was better. That opinion requires ... a different reality, hopefully induced by drugs (because one can stop doing drugs).

John Saunders 2010-02-25 23:08:21

I agree with John Saunders, everyone knocks SSIS but simple states it's terrible or the worst thing ever, but no reasoning. In truth, I like SSIS the best, mainly because of it's ability to load into SQL Server faster, and I've used all these ETL engines plus a couple more.

ajdams 2010-03-16 20:28:27

ansaurus

tags:

views:

answers:

Rhino ETL opinions vs Kettle and SSIS

related questions