What users are saying about
208 Ratings
208 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.3 out of 100

Likelihood to Recommend

SSIS

  • SSIS is particularly well suited for jobs that need to be consistent, repeatable, and error managed.
  • Ongoing extract, transform, load [ETL] jobs that are scheduled or manual.
  • One-time ETL with complex datasets.
  • Migrations of large datasets.
SSIS is not well suited for small or simple datasets that can be copied or exported safely to flat files for import. It is possible to do this but would generally take longer to build in SSIS unless there was a good reason to .remove manual handling of the data in transport or the action needed to be testable/repeatable.
Anonymous | TrustRadius Reviewer

Feature Rating Comparison

Data Source Connection

SSIS
8.6
Connect to traditional data sources
SSIS
9.4
Connecto to Big Data and NoSQL
SSIS
7.8

Data Transformations

SSIS
9.2
Simple transformations
SSIS
9.8
Complex transformations
SSIS
8.5

Data Modeling

SSIS
7.5
Data model creation
SSIS
7.6
Metadata management
SSIS
7.4
Business rules and workflow
SSIS
8.2
Collaboration
SSIS
7.0
Testing and debugging
SSIS
7.6
feature 1
SSIS
7.0

Data Governance

SSIS
8.3
Integration with data quality tools
SSIS
8.7
Integration with MDM tools
SSIS
7.8

Pros

SSIS

  • SSIS works very well pulling well-defined data into SQL Server from a wide variety of data sources.
  • It comes free with the SQL Server so it is hard not to consider using it providing you have a team who is trained and experienced using SSIS.
  • When SSIS doesn't have exactly what you need you can use C# or VBA to extend its functionality.
Anonymous | TrustRadius Reviewer

Cons

SSIS

  • SSIS memory usage can be quite high particularly when SSI and SQL server are on the same machine
  • SSIS is not available on any environment other than Microsoft Windows
  • SSIS does not function with any database engine back-end other than Microsoft SQL Server
Anonymous | TrustRadius Reviewer

Likelihood to Renew

SSIS

SSIS 10.0
Based on 3 answers
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
Luca Campanelli | TrustRadius Reviewer

Usability

SSIS

SSIS 9.2
Based on 8 answers
If you use any of the Microsoft tools, it is easy to get using and understand since it uses Visual Studio and SSMS to work with. There are extensions you can get and some of those can be difficult to work with but usually they slide in nicely. The one thing to understand though is there is some installation and configuration on the SQL Server side that can take some time.
Steven Gockley, MBA, MCSA | TrustRadius Reviewer

Performance

SSIS

SSIS 8.7
Based on 6 answers
You can, of course, accidentally make sloppy code or workflows but it’s not a tools issue if you run packages in an inefficient way. With a company of our size, we never had any performance issues but I can imagine for larger companies that this will have a greater focus.
Anonymous | TrustRadius Reviewer

Support Rating

SSIS

SSIS 8.1
Based on 8 answers
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.
Chris Morgan | TrustRadius Reviewer

Implementation Rating

SSIS

SSIS 10.0
Based on 1 answer
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
Luca Campanelli | TrustRadius Reviewer

Alternatives Considered

SSIS

Look for where you are going to load the data and from where are you extracting it. A lot of those who sell you the DB already have tools for ETL. I have heard good things at an enterprise level from great colleagues about Informatica, but honestly, I prefer SSIS.Although I did like TIBCO Jaspersoft and it can be mixed with TIBCO Spotfire for data analysis. If your ERP is SAP, then you must keep in mind using SAP BusinessObjects. As for free tools, and if you have a great and constant team of scripting (Perl, Python) engineers, then you can think about going open source.
Jose Pla | TrustRadius Reviewer

Return on Investment

SSIS

  • I use SSIS to automate tasks that I'm repeatedly asked to do. "Hey, can you go into the system and close any open orders that we've fully filled?" Sure....then I schedule a package to do that for me every hour so I'm never asked again. It saves me time, which gives value to the company.
  • It removes the risk of human error. When people build files and send them, there's the risk that it doesn't happen the same way every time or gets forgotten. With SSIS, you spend some up front time building a process, but then you deploy it and forget it (unless it emails you that there was an error. You are putting error handling in your ETL, right?). Very repeatable and consistent business solution.
Greg Goss | TrustRadius Reviewer

Pricing Details

SSIS

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Rating Summary

Add comparison