TrustRadius Insights for SQL Server Integration Services are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Efficient Data Synchronization: Users have consistently praised SSIS for its ability to efficiently manage small-scale data synchronization tasks, enhancing productivity in data workflows. The tool's streamlined approach to syncing data has been noted as a time-saving benefit by many reviewers.
Rapid Data Transfer to SQL Server: Several reviewers have highlighted the tool's swift data transfer capabilities to SQL Server, particularly emphasizing its efficient handling of batch processes. This quick data movement feature not only accelerates tasks but also contributes to smoother operations within databases.
Real-Time Message-Based Functionality: Users highly value SSIS for its real-time message-based features and seamless integration with SQL Server and Visual Studio, facilitating agile data processing. The system's agility in handling real-time messages has been commended for improving responsiveness and connectivity across platforms.
We are using the SSIS as a major data export/import & converter between different data sources, including relatively old legacy stuff out from 90th. The beauty of SSIS is really advanced capabilities of data converts and mix up the data from different sources with all respect to keys and data relations. We use this mostly as an addition to the SQL Server Express edition (as a part of the import/export wizard) but on the sandbox I doing the tests of SQL Server 2016 Standard edition to mix up several RDBMS for data extraction into one data warehouse.
Pros
Extraction and convert data from various sources
Pipelining in the data extraction process
Unions between different data sources akin one meta datasource
Cons
Some labels in Visual Studio snap-in for MS SQL Server are collapsed on non-English (German & Russian tested) locales.
Likelihood to Recommend
Well suited: all data extraction from file (spreadsheet-like) and RDBMS data sources, mix up them into one integrated meta-data source for future processing. Less appropriate: big key-value data storages processed slowly, and hard to make data mining through uniting non-RDBMS and RDBMS data sources naive way. The data from non-SQL databases should be prepared accordingly to be represented in a table-like way if possible.
We use SQL Server Integration Services to import data into and out of our main SQL server databases. This data comes from a variety of external sources and sometimes there is data format mismatch between source and destination. With an SSIS package, we can retain the mapping and data formats integrity from the source to the destination without having to go through the process every time.
Pros
Easy to manage projects and packages.
Ideal for repetitive tasks.
Can handle complex tasks consisting of multiple, diverse packages.
Cons
Include SSIS in the default installation of SQL.
The flexibility and different packages and options can make it confusing for first-time users.
Recommendations in the selections could make it easier to build a solution.
Likelihood to Recommend
Well suited and designed to enable flexible data extract and transformation to and from an SQL server. It works very well for repetitive tasks and it is easy to manage (and change) packages once built. The use of templates makes the initial startup process simpler.
SQL Server Integration Services (SSIS) is not easy for new users due to the plethora of options available.
VU
Verified User
General Manager in Information Technology (Non-Profit Organization Management company, 11-50 employees)
It is mainly used by technical analysts with the purpose of delivering data integration and reporting projects to customers. It addresses the need for complex multi-source data ingestion, data manipulation, and integration to a MSSQL database.
Pros
Visual programming makes configuration easy and accessible
The ability to code also allows users to implement complex logic for data manipulation and etc.
Easy integration with MSSQL Database instances.
Cons
Component properties are not very well defined, which makes the learning curve harder
As control flow and data flow often looking similar visually at first glace, it takes awhile to differentiate which one you are working on as users need to look at the tiny symbol and text on the tab to do so. A more straightforward color-coded or larger visual cue to differentiate between the two would make this easier.
Likelihood to Recommend
SSIS is suitable for MSSQL related projects/works due to how well it integrates and performs data manipulation. It is suitable for moderate data input ingestion rates but not suitable for projects where a high volume of data is required to be ingested and processed rapidly.
VU
Verified User
Analyst in Engineering (Information Services company, 11-50 employees)
I've used SSIS to support individual departments within an organization. Typically I use SSIS to automate migrating and transforming data from one location to another. SSIS has a diverse range of source and destination formats that makes it easy to move data between different systems. There are many add on tools for other source / destinations that are not out of the box. For example, Dynamics CRM.
Pros
SSIS allows you to run many processes in parallel. Thus, you can run multiple data flows simultaneously to increase the throughput of the migration process.
SSIS provides many tools for transforming data during the migration process.
Cons
The one issue that I have with SSIS is that sometimes the business logic gets baked into the SSIS package. This can make it harder to debug. In some cases this makes sense if the source and destination is not a database. However, when using a database as a source I prefer to manipulate and transform the data via sql and then simply expose the dataset to SSIS after the data has been prepared. I find it easier to write and debug sql directly rather than working in SSIS. However, in cases when a database is not involved then putting the business logic in SSIS makes sense.
Likelihood to Recommend
SSIS is well suited for any processes that can be automated to move data from a source to a destination. However, I don't think SSIS can work directly with Rest API's during it's processing. If that is required than it would be necessary to build your own custom SSIS component to enable this functionality. Extending SSIS to permit this is possible.
VU
Verified User
Consultant in Information Technology (Computer Software company, 11-50 employees)
SQL Server Integration Services is the go to tool for our Data Integration team for automating a number of disparate data imports. We deal with a number of file sources (Excel, CSV, TXT, etc) that need data transformed for import into our SQL databases. SSIS allows us to handle any number of file formats and types efficiently, and we can perform all data validations necessary to ensure utmost data integrity.
Pros
Handling upsert functionality (i.e. performing lookups against existing data to determine new versus existing records).
Automation of scheduled file imports. Essentially any consistent data source can be automated after a one-time SSIS package is set up.
Ability to handle a wide variety of data sources.
Cons
Excel data type handling - makes assumptions on a single data type where there might be multiple data types in a specific column.
Better handling of data schema changes - If you have column changes or additions in your data source, it does not always implicitly make those changes across all data transformation tasks within the package.
No reliable built-in functionality for SFTP connections.
Likelihood to Recommend
SQL Server Integration Services is particularly well suited for automating oft-used data transformation processes. Any transformation tasks that are performed manually on a consistent data source should be able to be automated using SSIS. It's also very well suited for DB to DB data migration, whether it be one-time ad-hoc requests or common scheduled tasks (i.e. migrating from test to production databases).
VU
Verified User
Team Lead (Computer Software company, 11-50 employees)
We use SQL Server Integration Services to pull data from FTP sites.
Pros
Our clients have branches and each branch generates a flat file and loads to a remote site from which we pull and consolidate the data and report from the consolidated data.
SSIS would allow [us] to execute a batch file which will pull the files and decrypt.
SSIS transformations are easy to use when [they] loop around the files in the same folder.
Cons
SSIS expressions are difficult to read and comprehend.
SSIS fuzzy loop up transformation performance needs to be optimized.
SSIS packages code should be easy to copy and modify so that it can easily be replicated just like BIML.
Likelihood to Recommend
Can SQL Server Integration Services (SSIS) perform multiple unrelated tasks within a package?