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.
SSIS pulls data from various locations (mostly SQL Server instances but also some flat files and SFTP), mainly for transforming the data and putting it in the data warehouse.
Pros
SSIS is good for small, simple data syncs.
SSIS is good for moving data quickly into SQL Server (good batch performance).
Cons
Very hard to diff for code review when changes are made.
Very buggy IDE (freezes in Visual Studio, doesn't always show what's in the underlying XML properly)
Lacking lots of features or more modern tools, like ability to monitor for changes to the source schema and apply them to the target.
Likelihood to Recommend
If you already have licenses for SQL Server and need to get data from A to B, especially if A and/or B is SQL Server, then SSIS could be a reasonable choice, especially if you can't use a cloud tool like Fivetran due to security concerns.
SSIS is an on-premise data transformation tool and the first major ETL tool we have used. We use it to ETL data from Workday, and other internal applications/databases to our internal databases. The product addresses the issue of getting data from CSV files from our SFTP and performing update/insert/delete operations on the data in our internal databases.
Pros
Connect to various sources
Basic transformations are included
Connect to various destinations
Cons
We still need plugins to connect to SFTP and other sources. Many vendors in the market give this by default
It's an ETL tool and the ability to do ELT or ETLTL means spinning up more pipelines and packages
It still has compatibility issues in Visual Studio 2017
Likelihood to Recommend
SQL Server Integration Services is well suited for anyone beginning to learn ETL. It's a great tool, to understand the nuances of setting data integrations and transformations. SQL Server Integration Services is not meant for ELT or ETLTL operations, natively. The workaround would be to have multiple packages/pipelines where one package performs the EL and the other package performs the T.
VU
Verified User
Manager in Information Technology (Design company, 5001-10,000 employees)
We are currently using SQL Server as our central relational database. Getting data from multiple sources to our data depository is smooth. We use SQL Server Integration Services to copy and download large files as well as to draw out and modify data from several sources of data like XML data files, DB2 databases, and relational data sources and then load the data into a single destination.
Pros
I am able to use the GIS tools to easily generate solutions without coding.
Built in tasks that speed up web developing.
SSIS enables automated data preparations.
Amazing integration with Microsoft tools.
Creation of ETL mapping.
Cons
It depends so much on the Microsoft environment and has integration issues with other formats like JSON and Excel.
Error messages are unclear, this makes us spend a lot of time figuring out what has gone wrong making the debugging process hectic.
Likelihood to Recommend
We have used SSIS to perform extensive data migration tasks from various sources like DB2 databases, SQL server databases... It works speedily making it easy for us to move data from one database to the other. It also has a GUI that helps us extract, transform, and clean data easily without writing code. It works well except for the error messages.
In our organization, we have two Microsoft windows servers. We integrate their data sync via SQL Server Integration Services. It's easy for us to migrate our data from one server to another server. The debugging capabilities are great, particularly during data flow execution. We can look into the data and see what's going on in the pipeline.
Pros
Encrypt files with SSIS and send them to various network locations this way we solve complex business problems.
We can migrate DTS packages to SSIS while choosing to run DTS packages using DTS runtime or incorporate DTS packages into SSIS this way we migrate DTS packages to SQL Server Integration Services.
We can transform data to make sure it complies with the rules of the database they are migrating to other servers with Integrations Services.
Cons
User-required automation needs much more scope.
Exporting numerous tables in CSV format has to be done one by one by manual.
Likelihood to Recommend
Helpful in connecting to various data sources and loading the combined data. More cost-efficient than other ETL tools of the same stature. Reduces the need for coding scripts.
We used Integration Services to extract and transform data from a wide variety of sources such as XML data files, flat files, and relational data sources, and then load the data into one or more destinations. We also used the graphical Integration Services tools to create business solutions for the firm.
Pros
Create Packages in SQL Server Data Tools
Reuse Control Flow across Packages by Using Control Flow Package Parts
Build Integration Services User Interface
Cons
We can improve Integration Services error messages, including a list of most Integration Services errors and their description.
Improvement to create custom event handlers for these events to extend package functionality.
Better support for tools and wizards helping with Legacy Package Deployment.
Likelihood to Recommend
Integration Services is very helpful to solve complex business problems by copying or downloading files, loading data warehouses, cleaning and mining data, and managing SQL Server objects and data. It provides Graphical tools for building packages. Also, it helps with the SSIS Catalog database to store, run, and manage packages for business solutions.
VU
Verified User
Director in Sales (Management Consulting company, 5001-10,000 employees)
As a BI / Data Analyst, I have to deal with multiple data source integrations independent of to live environment. So, I have to combine data query many query tables. I need to maintain the schemas of databases with multiple data sources.
Pros
Integration with multiple data sources
Creating Schemas
Data modeling
Data cleaning
Cons
Ease of use for initial get into application
Application Loading
Likelihood to Recommend
While integrating Google Ads FB ads and maintaining the cost analysis. it was quite easy and very smooth with PowerBI. I always use powerBI for Data Analysis reporting and SSIS is a very smooth experience to use large databases.
VU
Verified User
Analyst in Information Technology (Information Technology & Services company, 201-500 employees)
Being part of the Healthcare department, we need to automate the data transfer from and to the company and hospitals. SQL Server Integration Services, allowed us, to create a robust platform, to process millions of records from each hospital everyday, the whole year, just taking care of small incidents, such formats, not related to the SSIS, itself. So, we relied on this process for keeping the data and the collection, working efficiently and providing outstanding service.
Pros
Data transfer
Automation
Programability
Scheduling
Cons
Clarity on errors
Support
Likelihood to Recommend
Automation for data transfer, where you don't need to be moving or copying any data manually. Processing data, for ETL, so you can just get the files, using something like FTPs automation and the data will be processed, and then you can just work on your reports or do all the BI needed for the company
SQL Server Integration Services has been useful in implementing Extract, Load, and transform logic from various sources and destinations. we also use it to download data files from SFTP, FTP locations. We use it to refresh extract in tableau and run other 3rd party services via executing process tasks. It has been useful to address many other such challenges.
Pros
FTP Downloads.
Run 3rd party softwares.
Intuitive UI.
Cons
Need more connectors/sources/destination components.
Ability to support not just Microsoft services but others too.
More updates & new features.
Likelihood to Recommend
More suited for Full loads, use along with other Microsoft services, ETLs Less suited for: use along with modern software/services, Near real-time integration.
VU
Verified User
Engineer in Information Technology (501-1000 employees)
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.
SSIS is being used for data interchange. This includes using it for traditional ETL to a corporate data warehouse, as well as for the production or intake of flat files for interchange with external sources. Sources include traditional RDBMS, web services based cloud sources, and flat files. We are beginning the process of extending SSIS to the cloud in conjunction with Azure Data Factory.
Pros
Process flow.
Connection to a wide array of sources.
Cons
Built-in upsert component.
Better operability with source control systems.
Likelihood to Recommend
SSIS works great for 80+ percent of ETL use cases. It is particularly well suited for migrating and transforming data between traditional databases. If using the Azure cloud, it also has a number of built-in components to make that process easier. The base set of transforms are pretty robust and will perform most tasks with decent speed.