Currently not using any of the Informatica tools, so, I don't have a real way of comparing the tools. But comparison against Microsoft SSIS (SQL Server Integration Services) I'd say DataStage stacks favorably. DataStage is a powerful tool for ETL processes that integrates …
DataStage offers better integration capabilities without the need to write code manually. It also has a native ETL engine whereas MSIS requires a SQL Server. It has better integration capabilities with data quality, data profiling and data governance tools. The main drawback of …
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 …
Excellent Cloud data mapping tool and easy creating multiple project data analytics in real-time and the report distribution are excellent via this IBM product. Easy tool to provide data visualization and the integration is effective and helpful to migrating huge amounts of data across other platforms and different websites insights gathering.
There are always alternative options available to meet the demand for integration. In my opinion, SQL Server Integration Services has a wide variety of capabilities that makes it a very versatile tool for developing dependable integration strategies. When determining which tools to utilize, vendor interfaces may play a significant role, and technologies like PowerShell have been used by colleagues to aid in this decision. For even more user-friendliness, our SSIS solution additionally makes use of a third-party plugin.
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
Because it is robust, and it is being continuously improved. DS is one of the most used and recognized tools in the market. Large companies have implemented it in the first instance to develop their DW, but finding the advantages it has, they could use it for other types of projects such as migrations, application feeding, etc.
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.
It could load thousands of records in seconds. But in the Parallel version, you need to understand how to particionate the data. If you use the algorithms erroneously, or the functionalities that it gives for the parsing of data, the performance can fall drastically, even with few records. It is necessary to have people with experience to be able to determine which algorithm to use and understand why.
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.
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
It's obvious since they both are from the same vendors and it makes it easier and can get better rates for licensing. Also, sales rapes are very helpful in case of escalations and critical issues.
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 traditional scripting. Comparably free, but my own familiarity with trad scripts would be my final deciding factor. Perhaps with some further training on SSIS I would have a different answer.
