Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Talend Data Fabric
Score 10.0 out of 10
N/A
The Talend Data Fabric helps organizations to achieve and maintain complete, trustworthy, and uncompromised data, so that they can stay in control, mitigate risk, and drive value.
Technical Analyst BI II (Global Business Intelligence and Analytics - Data Infrastructure)
Chose SQL Server Integration Services (SSIS)
I've used several other ETL tools and they can all do the trick once you learn how to get around their shortfalls, including SSIS. I think the best reason to use SSIS is if you're already using Microsoft tools. They integrate well with each other and it's easy to understand how …
As I mentioned earlier SQL Server Integration Services is suitable if you want to manage data from different applications. It really helps in fetching the data and generating reports. Its automation make it very easy and time efficient. It works well with large database as well. But it doesn't work well with real time data, it will take some time to gather the real time data. I would not recommend using it in a real time/fast-paced environment.
Truly trusted contact center where the effective solution is always guaranteed. It is not a one-off fix to a specific data integration or management problem. It is a permanent and scalable solution to manage all of your data under a unified environment. Easy to use, great performance, used it for our internal data warehouse. Easy to build and connect to our data sources such as Salesforce, Netsuite, and Marketo.
It supports a wide variety of connectors (Systems/endpoints)
It provides great flexibility for developers as it not only has a lot of predefined ready to use the function but also provides the ability to use complex java code within the platform. Great tool if you have good developers available.
Connection managers for online data sources can be tricky to configure.
Performance tuning is an art form and trialing different data flow task options can be cumbersome. SSIS can do a better job of providing performance data including historical for monitoring.
Mapping destination using OLE DB command is difficult as destination columns are unnamed.
Excel or flat file connections are limited by version and type.
Some features should be revised or improved, some tools (using it with Visual Studio) of the toolbox should be less schematic and somewhat more flexible. Using for example, the CSV data import is still very old-fashioned and if the data format changes it requires a bit of manual labor to accept the new data structure
SSIS is a great tool for most ETL needs. It has the 90% (or more) use cases covered and even in many of the use cases where it is not ideal SSIS can be extended via a .NET language to do the job well in a supportable way for almost any performance workload.
At this moment the usability of Talend Data Quality is optimal, too bad I cannot say the same in the first three months, it was always a problem due to its steep learning curve, but what matters is being able to use it effectively at this precise moment.
SQL Server Integration Services performance is dependent directly upon the resources provided to the system. In our environment, we allocated 6 nodes of 4 CPUs, 64GB each, running in parallel. Unfortunately, we had to ramp-up to such a robust environment to get the performance to where we needed it. Most of the reports are completed in a reasonable timeframe. However, in the case of slow running reports, it is often difficult if not impossible to cancel the report without killing the report instance or stopping the service.
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.
Talend Data Quality gave us direct help in the learning process and prevented us from taking many more months to adapt and I appreciate this from the heart, I think that thanks to the support we can have very detailed reports that help increase the use of Talend Data Quality in the company.
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
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
The engine with which it works to process a lot of information is striking, the comparison also being the connectors it has for different RDBMS, which other tools do not count as they are GNU licenses or community editions. The friendly and intuitive environment is what catches the eye. that's why I choose Talend over any other tool
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.