The Informatica® Intelligent Data Management Cloud™ (IDMC) is designed to help businesses efficiently handle the complex challenges of dispersed and fragmented data to innovate with their data on virtually any platform, any cloud, multi-cloud and multi-hybrid.
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
Informatica Intelligent Data Management Cloud
SQL Server Integration Services
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Informatica Intelligent Data Management 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
Informatica Intelligent Data Management Cloud
SQL Server Integration Services
Considered Both Products
Informatica Intelligent Data Management Cloud
Verified User
Engineer
Chose Informatica Intelligent Data Management Cloud
Having used SQL Server Integration Services (SSIS) in the past, Informatica Cloud was a huge-step up in functionality, usability and performance. Hands-down, Informatica Cloud is a much more robust product overall. While SSIS is well-suited for specific instances (i.e. SQL …
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 …
Informatica Cloud is a great tool for use when data must be formatted consistently. Once configured, it is very robust and reliable. It is also well-suited for an organization without a robust IT staff to maintain a full server infrastructure. It offers a cost-effective approach to high-quality data integration for even the largest organizations. Organizations without staff experienced in data analytics may find it challenging to take advantage of the more complex results of this tool.
Ideal if the company is already a Microsoft shop, so chances are that it is free with SQL Server. Also, good for moving data between on premise systems. Not ideal for moving data to the cloud. No functionality out of the box to work with REST APIs. Stable product but definitely not the future
Once the secure connection is established it’s quite easy to operate and create new jobs. The controls are simple, and we appreciate the fact there are not a lot of complex fine-tunings required. Navigation is also easy, and we enjoy the ability to open multiple tabs in the browser to work on multiple projects.
The monitoring functionality works well to help track the progress of the jobs, again, without too much complication. In a fast dev environment, speed is essential and we quickly seeing the status/progress of jobs as well as any errors if the jobs fail helps us maintain speed.
The web interface is a lot easier to interact with than the client/on-prem version. Putting much of the heavy lifting of interacting with the tool onto the shoulders of the browser makes it easier to keep multiple sessions open and get in/out quickly without having to VPN into the office.
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.
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.
I've never had trouble getting into contact with Informatica's support for technical help. I give it a nine because it does pretty well for mid to enterprise-scale workflows.
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
First, the wizard is easy to use making the learning curve for simple ETL tasks nice. Second, since Informatica is mature there are a good variety of connectors available. Finally, we have driven some fairly complex ETL solutions using only the cloud.
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.