Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase «««1234

Talend vs. SSIS: A Simple Performance Comparison Expand / Collapse
Posted Wednesday, October 23, 2013 11:46 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, April 7, 2016 2:52 PM
Points: 6, Visits: 60
I have to admit that I found this review close to useless. Here's why: It's not because of the tests, although the simplistic tests may or may not be valid. The reason I found this "comparison" between two products so unhelpful was the obvious, and rather flagrant, bias this developer had against non-Microsoft products. Comments like "abhor Java" do more damage in my mind to his argument than it helps. I use SSIS and I like it. It's not perfect but I does a very good job. But I'm not just a Microsoft developer. As well as being a SQL Server developer, I am equally capable (my own assessment of course) as an Oracle developer.

In spite of the results, this only made me want to find out about Talend. Thanks for the comparison and introducing me to a new product.

Post #1507882
Posted Monday, October 28, 2013 12:29 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, November 3, 2013 1:06 AM
Points: 1, Visits: 11
Just wondering, why in Talend job a tFileOutputMSDelimited (multi - schema) is used instead of a simple tFileOutputDelimited (single - schema). It wouldn't most probably change a lot, but well, it would be more transparent.

Have to agree with this comment. The tFileOutputMSDelimited component adds a huge amount of overhead and also would account for the out-of-memory error. Using a simple tFileOutputDelimited component would be far more efficient and use only a nominal amount of memory. It would also be more efficient to do the filter in tMap instead of as a separate component.

However, in general, Talend - because it generates code and is very flexible - has a bit of overhead in tracking the progress of the job through the components.
Post #1508755
Posted Tuesday, December 3, 2013 3:44 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Sunday, July 19, 2015 3:49 PM
Points: 76, Visits: 8
Liked the article. I too was an MS only person for about 15 years. But, have expanded to much more in the last 3-4 years or so (IBM DataStage, Informatica, and Talend). Just getting into Talend for last 1 year, and like it a lot.

Think the author is trying to get an apples to apples comparison. Though it might be better to have both tools write to a separate database instance as the target (maybe Oracle or DB2 to make it neutral) as most ETL will write to a RDBMS target.

The biggest thing missing for me is, both tests should be run as scheduled jobs and not using the designer. They will behave much differently when not run through the GUI. The comments about requiring tuning the server or OS for Talend, think are not that import, they are 1 time steps that usually our infrastructure people know how to tune for java/linux. We’re not talking about some tuning you have to do inside each job, just the server as a whole.

Talend has a lot of benefits, including tons of unique components (with more functionality added each release) that would be hard to do the same thing in SSIS.
Post #1519434
« Prev Topic | Next Topic »

Add to briefcase «««1234

Permissions Expand / Collapse