Talend Open Studio was an open source integration software, used to build basic data pipelines or execute simple ETL and data integration tasks. Qlik and Talend discontinued the service in early 2024, and it is no longer available.
I prefer to use Talend Open Studio over SQL Server Integration Services because of the ease of use and wider connection library opportunities. By leveraging Talend Open Studio we are able to connect to a much wider set of source data as well as rapidly designing and deploying …
Microsoft SQL is ubiquitous, while MySQL runs under the hood all over the place. Microsoft SQL is the platform taught in colleges and certification courses and is the one most likely to be used by businesses because it is backed by Microsoft. Its interface is friendly (well, as pleasant as SQL can be) and has been used by so many for so long that resources are freely available if you encounter any issues.
For quick daily integrations Talend is a very good tool and it makes development time so short and easy. Citizen developers who are not great programmers can pick up and start using Talend Open Studio within weeks. It's well suited for all kinds of data migration between various systems. It is less appropriate for smaller synchronous services where you need to trace the complete transaction and how data moved between them. It's also less appropriate for small data movements where other tools can be easier to use and manage.
Microsoft SQL Server Enterprise edition has a high cost but is the only edition which supports SQL Always On Availability Groups. It would be nice to include this feature in the Standard version.
Licensing of Microsoft SQL Server is a quite complex matter, it would be good to simplify licensing in the future. For example, per core vs per user CAL licensing, as well as complex licensing scenarios in the Cloud and on Edge locations.
It would be good to include native tools for converting Oracle, DB2, Postgresql and MySQL/MariaDB databases (schema and data) for import into Microsoft SQL Server.
The community is not that up to date and forum is not that great in response. Probably we should make people aware of the tool more on how to use and its implementations.
Talend crashes when transforming a lot of data (millions of rows).
Proper training documentation is a must for talend which is currently lagging. This will help users to learn more about Talend and use it effectively.
We understand that the Microsoft SQL Server will continue to advance, offering the same robust and reliable platform while adding new features that enable us, as a software center, to create a superior product. That provides excellent performance while reducing the hardware requirements and the total cost of ownership of our solution.
There is no licence requirement for Talend Open Studio. So, this is not relevant question. However, if you are asking whether we will use Talend in future. Yes. We will continue to use it. It's very powerful free tool which caters to all our extra, transform, load capabilities. We just love Talend for it's great functionality and ease of use.
SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.
Talend Open Studio is based on Eclipse and is full of redundant procedures to do one thing, like when installing libraries. Sometimes I cannot manually download the libraries that it can't find.
Many times, Talend freezes. When you give a cancel command, it takes several minutes to stop. It also takes a great toll on our PC with 16 GB of ram and I7 CPU, even in idle status. If you are downloading Maven Jar/Libraries, you cannot do anything and have to wait until the task is finished.
We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.
Talend Open Studio is free and we are not using the enterprise version which comes with licence and support. So, mostly depend on the open source community for any issues that we face. The document is good and we didn't have to use any support so far. We did evaluate the enterprise version and so far sticking to the free version.
Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.
[Microsoft] SQL Server has a much better community and professional support and is overall just a more reliable system with Microsoft behind it. I've used MySQL in the past and SQL Server has just become more comfortable for me and is my go to RDBMS.
Informatica has a limited number of components that you can use. This places a heavy limitation on the capabilities of Informatica. On the other hand, Talend allows you to create your own custom components using Java. For businesses that need to perform a wide variety of data operations, it can be quite useful to have the option of creating your own custom components to satisfy business needs.
Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.
I delivered projects the client did not believe were possible, and I provided intermediate value by providing visibility to hidden data problems in their systems they could not detect before.
I was able to work 3 projects at a time, pausing gracefully in one while switching to the other, with minimal effort.
