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.
Data Engineering and integration. Move data between different on-premise servers no matter the platform. Since we have an Enterprise Agreement with Microsoft, it does not cost any extra to use SQL Server Integration Services unlike Azure Data Factory or Informatica. Wherever data transfer is involved, it is the de-facto standard in our company.
Pros
Easily connects to source and destination systems
GUI interface - so minimal learning curve
Script task feature enables extensibility and access to .NET framework
Cons
Zero enhancements by Microsoft in a very long time
Has fewer connectors compared to Power BI or ADF
Not ideal for handling huge datasets
Likelihood to Recommend
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
VU
Verified User
Professional in Information Technology (Oil & Energy company, 501-1000 employees)
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.
We use SQL Server Integration Services (SSIS) as part of our on-premise Data Warehouse architecture. We have an ELT pattern and SSIS is used almost exclusively for the Extract and Load steps. Almost all packages are generated using BIML (Business Intelligence Markup Language) as a means of templating and then scripting them.
Pros
Easily connect with a wide variety of sources.
Provide control and flow to job execution order.
Able to extend functionality through scripting tasks.
Cons
Not flexible when source/target tables and file formats change.
Inflexible with regards to varying data types when Excel spreadsheets are used as a source or columns are added (as per previous item).
Occasional issues around mixed development and production x86/x64 run times can be frustrating.
Likelihood to Recommend
I do not think that SQL Server Integration Services (SSIS) is great for complex dependency management and scheduling for an entire DW load. However, it is great for smaller units of work and particularly where moving data between systems is required due to its extensive and extensible connectivity options. That said, it is obviously focused on traditional on-premise systems and cloud-based environments are likely to prefer using the next-generation version of SSIS being Azure Data Factory (ADF).
VU
Verified User
Professional in Information Technology (Leisure, Travel & Tourism company, 201-500 employees)
A good tool for SQL server query and data migration. The way it stores data and makes it easier for the user to write queries over the server. Compatibility with different BI tools is awesome as it is easy to integrate Microsoft SQL servers with different BI tools like google data studio and PowerBI.
Pros
Assists in connecting to several data sources and loading the resulting data.
Less expensive than other ETL tools of same stature.
Does away with the requirement for coding scripts.
Cons
There isn't a lot of room for building user-required automation.
Some activities need manual labour, such as exporting multiple tables in CSV format one at a time.
Likelihood to Recommend
1. Combining and integrating data from a variety of sources. 2.There is no additional necessity to learn anything other than SQL. 3. Assists in the analysis of client data by bringing it all together in one place. 4. Data leaks of clients' personal information are avoided. It is HIPAA compliant and it has very secure server.
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.
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)
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)
In my department, we design and manage ETL processes. We use SQL Server Integration Services (SSIS) to design a data warehouse. To create a data warehouse, we can make the stage layer and DWH layers with the SSIS ETL tool. We create data marts using aggregate functions in the SSIS ETL tool. In addition, we use the SSIS ETL tool to move data between databases.
Pros
Data migration is pretty fast.
SQL Server is highly compatible with the database.
Cons
We receive errors in moving JSON data to the database. It does not work efficiently in JSON-related data.
ODBC connections give a connection error after a certain period of time.
Likelihood to Recommend
For enterprise business intelligence projects, the SQL Server Integration Services ETL tool is a logical choice to move your data to the data warehouse on a daily basis. The SSIS ETL tool has enough functions and capabilities to design the data warehouse. If you want to send your JSON data to the database, SSIS does not work here.
The IT department at our organization uses SQL Server Integration Services. We use SSIS to perform extract, transform, and load (ETL) data operations. Our primary use is to move data from a source system or database, restructure the data to optimize it for reporting, and store it in a database instance used for reporting.
Pros
Handles multi-step, complex data moves.
Pulls from a variety of data sources.
Add-ons are readily available to extend their usefulness.
Integration with SQL Server and data tools.
Cons
The package publishing feature has gotten better over the years, but it could still be simplified.
Incorporating features from add-ons into the standard application would be helpful (mostly in relation to data sources).
Easier configurations for multiple publishing targets (dev/test/prod) with associated data connections.
Likelihood to Recommend
SSIS is well-suited for scheduled data loads, such as scraping web pages for currency rates or storm-related delivery delays and writing the results to an application database or copying transactional data from a source system, optimizing it for reporting, and writing to a reporting server. SSIS is also great in helping to combine data from disparate sources to build a deeper data analysis platform.
VU
Verified User
Supervisor in Information Technology (Chemicals company, 51-200 employees)
We use SSIS in a number or different use cases. 1. Traditional ETL for our data warehouse. 2. Automate reporting. We have a number of reports that go out to thousands of customers daily. We have implemented SSIS to run these. 3. Application integration. With SSIS we are able to quickly integrate from our order entry and operations software into our ERP and Financial software.
Pros
It sits inside of Visual Studio and SSMS so you have a consistent look and feel across toolsets
Extensions. We use Pragmatic work transforms that seamlessly fit into SSIS to make certain tasks easier
Performance. SSIS is not the fastest tool out there but it is more than enough for our needs and since it is bundled with SQL Server you get great value.
Cons
Funny thing, working with Excel requires hacks and work arounds. Really wish Microsoft would fix this.
More transformations to reduce the need of 3rd party tools. Tasks like SFTP would be nice.
Likelihood to Recommend
If you are a SQL Server shop, it is almost not even a question. The tool slides in nicely and is fairly easy to get going and implement. I have used it for Data Warehousing, Report Automation, DBA Task Automation, System Integrations and even Web Testing. It is extremely flexible and anyone working heavily with SQL Server should really look at using it.