Skip to main content
TrustRadius
SSIS

SSIS

Overview

What is SSIS?

Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.

Read more
Recent Reviews

Worth of money

10 out of 10
June 23, 2022
Incentivized
As a BI / Data Analyst, I have to deal with multiple data source integrations independent of to live environment. So, I have to combine …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 11 features
  • Connect to traditional data sources (53)
    8.8
    88%
  • Simple transformations (53)
    8.5
    85%
  • Complex transformations (52)
    7.7
    77%
  • Testing and debugging (48)
    6.1
    61%
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is SSIS?

Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

26 people also want pricing

Alternatives Pricing

What is Clear Analytics?

Clear Analytics is a business intelligence solution that enables non technical end users to perform analytics by leveraging existing knowledge of Excel coupled with a built in query builder. Some key features include: Dynamic Data Refresh, Data Share and In-Excel Collaboration.

What is Vertify?

VertifyData is a cloud-based integration platform with core integration capacities, including a drag-and-drop interface and real-time synchronization. It also offers over 80 prebuilt connectors and templates, plus customizable integrations for scaling businesses.

Return to navigation

Product Demos

Demonstration of Multicast transformation in SQL Server Integration Services (SSIS)

YouTube

SSIS Tutorial Part 78- What is Multicast Transformation in SSIS (Quick Demo)

YouTube

SSIS Tutorial Part 119-Execute SQL Task (Full Result Set) Demo in SSIS Package

YouTube

SSIS Tutorial Part 72- What is Conditional Split Transformation in SSIS (Quick Demo)

YouTube

SSIS Tutorial Part 02- How to Load Tab Delimited File To SQL Server Table in SSIS Package

YouTube
Return to navigation

Features

Data Source Connection

Ability to connect to multiple data sources

7.5
Avg 8.3

Data Transformations

Data transformations include calculations, search and replace, data normalization and data parsing

8.1
Avg 8.4

Data Modeling

A data model is a diagram or flowchart that illustrates the relationships between data

7.4
Avg 8.1

Data Governance

Data governance is the practise of implementing policies defining effective use of an organization's data assets

6.9
Avg 8.2
Return to navigation

Product Details

What is SSIS?

SSIS Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.

Reviewers rate Connect to traditional data sources highest, with a score of 8.8.

The most common users of SSIS are from Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(258)

Attribute Ratings

Reviews

(1-9 of 9)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
Incentivized
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.
  • FTP Downloads.
  • Run 3rd party softwares.
  • Intuitive UI.
  • Need more connectors/sources/destination components.
  • Ability to support not just Microsoft services but others too.
  • More updates & new features.
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.
February 17, 2020

SSIS Just Works

Score 8 out of 10
Vetted Review
Verified User
Incentivized
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.
  • Process flow.
  • Connection to a wide array of sources.
  • Built-in upsert component.
  • Better operability with source control systems.
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.
Steven Gockley, MBA, MCSA | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
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.
  • 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.
  • 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.
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.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Even though we are a smaller company, we use this huge army Swiss knife to accomplish a number of technical IT tasks. First and foremost we use it to integrate systems like MS CRM and SAP, constantly enhancing the data flow and making tasks easier to accomplish for the users. Secondly, I personally use it clean up data and maintaining my BI ETL scripts running out 12-year-old data warehouse for our analysis cube. The actual tool is currently only in use by the IT department by using Visual Studio (BIDS).
  • Almost no programming is needed, like drawing simple flow diagrams.
  • If you want to be more advanced you can add some VB or C# programming if needed.
  • Microsoft tool using all the great connectors, using any data source
  • Easy to add a third part like Cozyroc
  • File handling
  • Integration with office tools could always be improved, MS, as usual, provides these 80% solutions to make room for third vendors.
  • Error message or event handling, better messages and link to processes.
Any integration tasks in a Windows environment like AD or application integration, DB integration, etc. The drag and drop workflow and easy language, for example, derived data changes are so easy to make that it reminds of Excel functions. Full flexibility to draw up any workflow and easy troubleshooting using the data viewer.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
In my work in the health care field, we use SQL Server Integration Services as our default ETL tool of choice for pulling data into SQL Server from Teradata, Oracle, flat file and other SQL Server databases, and for creating data extracts to send to our clients, typically in the form of flat files.
  • 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.
  • SSIS has been a bit neglected by Microsoft and new features are slow in coming.
  • When importing data from flat files and Excel workbooks, changes in the data structure will cause the extracts to fail. Workarounds do exist but are not easily implemented. If your source data structure does not change or rarely changes, this negative is relatively insignificant.
  • While add-on third-party SSIS tools exist, there are only a small number of vendors actively supporting SSIS and license fees for production server use can be significant especially in highly-scaled environments.
SQL Server Integration Services is extremely well built for creating packages to run ETL operations in environments where the structure of the source and/or destination data never or rarely changes, however, it tends to be difficult to maintain packages in production environments where the structure of the data changes frequently.
Hung Nguyen | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
I cannot say for the whole organization, but we use SSIS for just about all our automation processes. When managing a large data warehouse it is incredibly useful to automate the ETL process. We primarily use it for the data warehouse, but it's versatile enough to use for other automation tasks, reports, and notifications.
  • Clear GUI and ETL workflow. It's very easy to understand how the data is being managed. When pulling up a SSIS solution that someone else has created, it's very easy to see what's going on-- how the data is extracted, how it is transformed, and how it's being loaded.
  • Deploying scripts. Once a proper package store is configured, you just need to hit deploy and it handles the rest. It's also flexible enough that you can still use SSIS packages without using an SSIS DB for version control by calling them through the file system. Or if you're one of those people who love batch scripts, you can also execute the packages through command line.
  • SSIS Package Store. It's a great way to manage your versions and deployments. Bonus is that if you use a package store, it'll also give you error reports after the fact if a package fails for debugging. It'll tell you exactly what step failed and why.
  • I think it handles undefined/dynamic data sources poorly. Considering that we use it primarily to ETL data from other systems across the whole organization to bring into our BU's data warehouse, we sometimes have issues when the source has changed. If someone adds a column without letting us know, we'll need to modify the SSIS packages.
  • Sometimes the error codes are vague or cryptic. When debugging a SSIS package I have to google the code or error message and hope someone has a similar issue on stack overflow.
  • SSIS really only works if you're already using a lot of Microsoft Products like Microsoft SQL Server or SQL Server Reporting Services. As mentioned in the name of the application, "integration services", it's designed to integrate your products together so that you can get the most out of it.
As mentioned in the pros and cons, SQL Server Integration Services is great when you're running a Microsoft stack. We're loading data from all over into our data warehouses and moving them between other SQL instances all the time. I can whip up a package and deploy it in less than 5 minutes to get our data moving between SQL servers. It integrates really well and is flexible enough that you can supplement any lacking functionality using third party plugins or building your own tools. Although this has been solved in later iterations, SQL Server Data Tools (which is used to build SSIS packages), did not have the functionality to download files from an FTP server using SFTP. I built a C# app that I could run using SSIS.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
SSIS is used by a lot of people within our technology department, but it is used heavily by our developers. We utilize this tool to move data between servers as an alternative to using a linked server and also to migrate data into our production systems from third party databases.
  • We use SSIS as a tool to help convert and migrate data from third party systems into our internally developed CRM system.
  • We use SSIS to move data from server to server, where a linked server is not present.
  • SSIS allows us to import tables directly from other sources (Access, Excel, etc.) to our Microsoft SQL environments.
  • SSIS is utilized to export data from our SQL servers into Access database backups for our clients who request backups of their data.
  • Although it's better than the old DTS, I think some more default integrated data sources/targets would be beneficial.
  • Integration with MySQL would be great. Currently we have to use Microsoft SQL Server Migration Assistant for MYSQL to get this done. If this was integrated into SSIS, it would alleviate the need for the other program.
SSIS is great for ETL projects, for exporting/importing data into MS SQL, and for moving data between servers. It's an excellent tool for those types of projects and scenarios.
Luca Campanelli | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
In our department we use SQL Server Integration Services daily. The main use is to do data processing for several ETL processes. Thanks to the use of SQL Server Integration Services we can upload data to the data warehouse in different ways such as a bulk load or with incremental loads thanks to the use of SCD task data.
  • High data load speeds
  • Many data processing modes
  • Many data sources and destinations data possible
  • For some tools you need to integrate third-party packages
  • Depending on the version you must have the right visual studio version to develop and deploy
  • Not really intuitive
SQL Server Integration Services is optimal for any process of data extraction, data transformation and data loading, and can be used quickly for massive loads. It can be used for scheduled and incremental processes. It is not optimal for data structures that continuously change their structure because in this case it requires continuous changes and deploys.
October 27, 2015

SQL BI Stack review

Nurvin Flowers | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
Used across the organization to move data, develop data marts and build front end reports
  • There is flexibility to Transform various data. There are also templates that help to guide you in using best practices such as building TYPE 2 loading of Data Warehouse tables
  • There are many transformation features that allow for sorting, lookups, using a variety of data sources and targets. It is a full featured product.
  • There are a lot of properties that allows you to customize data flows to suit your needs.
  • Having to sort prior to merging is a pain.
  • Working on very large data sets approaching 1 billion records require a lot of pre-planning. Teradata handle large data sets better
  • Error messaging is sometimes not explicit enough. "Something went wrong" is one of my "favorites" that I have seen
Well suited for data sets that are not too large < 500,000,000. Not well suited for handling very large data sets.
Return to navigation