The Qlik Talend Cloud suite of solutions offer data integration, data quality, application integration, and data governance that work with key data sources, targets, architectures, or methodologies to ensure business users always have trusted and accurate data.
N/A
SSIS
Score 8.0 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Pricing
Qlik Talend Cloud
SQL Server Integration Services (SSIS)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Qlik Talend Cloud
SSIS
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Qlik Talend Cloud
SQL Server Integration Services (SSIS)
Considered Both Products
Qlik Talend Cloud
Verified User
Anonymous
Chose Qlik Talend Cloud
Talend has many built-in components that reduce the development work. We were able to complete the project sooner than expected. Easy to on-board resources as it is straightforward to use. We can manage all the pipelines in the cloud with simple alerting. No major downtimes. …
In comparison with the other ETLs I used, Talend is more flexible than Data Services (where you cannot create complex commands). It is similar to Datastage speaking about commands and interfaces. It is more user-friendly than ODI, which has a metadata point of view on its own, …
SAP Business Object Data Services is another ETL offering that I have used before Talend. The biggest advantage is that Talend is open source and very user-friendly. SAP BODS needs to improve on the user interface. Also, it works well with relational databases but is not very …
Data Preparation is something which can improved and connectivity with more visualization tools are few factors which can be improved. As Talend Data Integration becomes more cloud focused, the gap in features / functionality widens between on-premise functionality and the …
Talend is the best for ETL out of all the other products we looked at. Of course, it is not meant for synchronous services. But, batch jobs that we schedule and run on bulk data are the best fit for Talend Data Integration. Though Talend does not provide a preview of …
Most other tools of similar nature work well for small and medium sized data warehouses, but fail to maintain performance for very large data warehouses. However, Talend works decently well on large data as well. On the other hand, there are software tools like Oracle Data …
Talend is much versatile in assimilating various different business use cases. It covers more functionality and is packed with tons of features to explore. It has the ability to fine tune to each project, and not be a one-fits all solution. Problems with Excel, is that it is …
There are code building and code conversions internally in most of these ETL tools. The repository is an overhead in the ETL process. There may be a need for a full-time administrator to manage deployments and monitor jobs. With Talend, it seems to be transparent with the pure …
Compared to Microsoft SQL Server Integration Services (SSIS) talend gives developers much more tools and flexibility in order to achieve different ETL processes. For instance, SSIS, separates processing from data management, and Talend mixes both stages so that you can perform …
Talend has all the data integration features needed for an enterprise along with big data integration. It stands tall as a data integration suite and has a low cost as compared to some of its commercial counterparts. Talend does not have reporting tools like Pentaho but its …
Both are very similar. Azure is cloud based. It is easier for the organization who uses cloud based application. The SQL Server Integration Services is cost effective. Azure was more on the expensive side for our organization. Azure was a little complex, it needed special …
I think SQL Server Integration Services is better suited for on-premises data movement and ADF is more suited for the cloud. Though ADF has more connectors, SQL Server Integration Services is more robust and has better functionality just because it has been around much longer
Fivetran, Stitch, and Etleap are all 1000x more modern than SSIS and 100x less aggravating. While those tools are mainly used to sync data rather than transform it, the ELT model works much better than the ETL model in most situations.
We just selected SSIS because we use SQL Server Management System (SSMS) to manage our database. As SSIS is a component of the Microsoft SQL Server there are no problems with integration and everything works perfectly. In addition, we don't have to learn how to use another …
Low-cost relative to other products - in fact, zero cost if one is considering the license cost as being for the database engine with Integration Services added on. It has a comparable range of functionality and performance and as such it's a 'no-brainer' to use SSIS over …
SnapLogic and Azure Data Factory are better than SQL Server Integration Services mostly because they are Integration Platform as a Service (IPAAS) services, whereas SQL Server Integration Services is an on-premise. So the basic differences such as, need a VPN to connect to the …
SSIS is similar to Alteryx and Informatica PowerCenter in a way because these are all drag-and-drop ETL tools with similar functionality. Alteryx is a step ahead because it has some advanced ETL functionalities including statistical calculations etc. and a better ability to set …
Alteryx Designer is easier to use for machine learning models. The functionality of drag and drop is the most valuable. It is a very user-friendly tool that can be understood easily. My teams also work with other solutions, such as Integration Services, and these solutions are …
I had nothing to do with the choice or install. I assume it was made because it's easy to integrate with our SQL Server environment and free. I'm not sure of any other enterprise level solution that would solve this problem, but I would likely have approached it with …
SAP Business Objects was a primary concurrent software against the MS SSIS but it has a more steep learning curve and requires additional investment into the SAP-related software infrastructure. With SSIS one can start easily with simple data extraction / DTL tools of Express …
I personally prefer SSIS. There are items that each do better than the others, but the ease of use of SSIS, along with its extensibility to 3rd party, ability to write any code required in the tool, and uses the same IDE for the MS BI suite (more of an issue if you're not a …
I used the Pentaho Data Integration (PDI) ETL tool. The PDI ETL tool does not have a public user collection like the SQL Server Integration Services(SSIS) ETL tool. Therefore, you may not be able to find instant solutions for your problems. But it has advantages over the SSIS …
SQL Server is already in our wheelhouse so it only made sense to utilize the tools we already had available to us--SSIS, SSAS, & SSRS. Other non-technical users seem to be more comfortable using alternatives to SSIS. However, these alternatives are not as good as SSIS at …
These are all great products and, honestly, can move data faster. They include more enterprise features and have some great qualities about each. However, they all cost a lot depending on the implementation you need. With SQL Server Integration Services, you do not have any …
When looking to evaluate different options, we looked first to the experience and software we had in-house that would accomplish the job. When assessing alternatives outside we were looking for the tool that would offer the most flexibility.
It’s basically a free tool and it has more features than anyone would ever need. If you look online for answers for SISS packages you will find a world of information that can cover almost any situation for your business. This tool can be used in any business and it provides …
SSIS is a very basic, developer-oriented ETL tool and while it lacks many of the nice UX features of its competitors it is a powerful tool that comes as a part of SQL Server and, in the hands of experienced developers with domain knowledge, can meet most organizations' ETL …
SSIS and Denodo differ in their approaches to ETL and Data integrations. SSIS is more affordable from a cost and licensing perspective (if you have Microsoft licensing), but Denodo is no slouch. If you go with Denodo, you are not creating data, there are pros and cons to …
SQL Server Integration Services does a good job for our SQL Server environments and was selected for that reason. For a SQL Server-only implementations, I would recommend SQL Server Integration Services. When we compared SSIS to other ETL providers against SQL Server, SSIS was …
The same way you design data integration job can be used to design services. It is easy to enhance by custom components and can adapt to all requirements. Talend Data Integration connects to [a] multitude of data sources and streaming service. Very easy interface to design complex applications without spending much time on coding. Easy to learn and master. Talend constantly strives to better itself by adding more features and functionalities.
Ideal for daily standard ETL use cases whether the data is sourced from / transferred to the native connectors (like SQL Server) or FTP. Best if the company uses MS suite of tools. There are better options in the market for chaining tasks where you want a custom flow of executions depending on the outcome of each process or if you want advanced functionality like API connections, etc.
We used Talend to ETLing the data from myriad sources such Oracle Database, Clarify, Salesforce, Sugar CRM, SQL DB, MQ, Stibo Step, FTP, Netezza, and Files.
We leverage Talend transformation capabilities for stitching the data , unions and join
We successfully created the final unified set that can be used by business
SSIS is responsible for running core business processed managing core business data. It can be managed, improved and expanded using minimal internal resources. It is also able to support all of our current data infrastructure. Replacing SSIS would be time consuming and costly with no apparent ROI.
We use Talend Data Integration day in and day out. It is the best and easiest tool to jump on to and use. We can build a basic integration super-fast. We could build basic integrations as fast as within the hour. It is also easy to build transformations and use Java to perform some operations.
It is easy to learn, works great on many features, but needs improvement on ETL troubleshooting and performance monitoring functionality. Great tool on Microsoft stack. it is great with simple, structured datasets. Once logic gets fancy like nested conditionals complex joins, reusable transformations, versioned logic …SQL Server Integration Services (SSIS) packages become hard to read and harder to maintain. Source control is painful. Errors can be cryptic Logging takes effort to set up well Debugging in production is limited.
Raw performance is great. At times, depending on the machine you are using for development, the IDE can have issues. Deploying projects is very easy and the tool set they give you to monitor jobs out of the box is decent. If you do very much with it you will have to write into your projects performance tracking though.
Good support, specially when it relates to PROD environment. The support team has access to the product development team. Things are internally escalated to development team if there is a bug encountered. This helps the customer to get quick fix or patch designed for problem exceptions. I have also seen support showing their willingness to help develop custom connector for a newly available cloud based big data solution
The support, when necessary, is excellent. But beyond that, it is very rarely necessary because the user community is so large, vibrant and knowledgable, a simple Google query or forum question can answer almost everything you want to know. You can also get prewritten script tasks with a variety of functionality that saves a lot of time.
The implementation may be different in each case, it is important to properly analyze all the existing infrastructure to understand the kind of work needed, the type of software used and the compatibility between these, the features that you want to exploit, to understand what is possible and which ones require integration with third-party tools
Talend has many built-in components that reduce the development work. We were able to complete the project sooner than expected. Easy to on-board resources as it is straightforward to use. We can manage all the pipelines in the cloud with simple alerting. No major downtimes. Connectors to all new applications in the market.
Both are very similar. Azure is cloud based. It is easier for the organization who uses cloud based application. The SQL Server Integration Services is cost effective. Azure was more on the expensive side for our organization. Azure was a little complex, it needed special training to use it. Azure was not accurate with complex data.
It’s only been a positive RoI with Talend given we’ve interfaced large datasets between critical on-Prem and cloud-native apps to efficiently run our business operations.
Without this, we would have to manually update a spreadsheet of our SQL Server inventory
We would also have poor alerting; if an instance was down we wouldn't know until it was reported by a user
We only have one other person who uses SQL Server Integration Services , he's the expert. It would fall to me without him and I would not enjoy being responsible for it.