My main use case for SSIS is reporting. I pull reports from warehouse management and various entities to ensure that everything aligns with the reports.
SSIS is a versatile tool for data integration tasks like ETL processes, data migration, and real-time data processing. Users appreciate its ease of use, data transformation tools, scheduling capabilities, and extensive connectivity options. It enhances productivity and efficiency within organizations by streamlining data-related processes and improving data quality and consistency.


| Product | Mindshare (%) |
|---|---|
| SSIS | 4.0% |
| Informatica Intelligent Data Management Cloud (IDMC) | 3.8% |
| Informatica PowerCenter | 3.6% |
| Other | 88.6% |
| Company Size | Count |
|---|---|
| Small Business | 21 |
| Midsize Enterprise | 16 |
| Large Enterprise | 36 |
| Company Size | Count |
|---|---|
| Small Business | 413 |
| Midsize Enterprise | 173 |
| Large Enterprise | 514 |
SSIS was previously known as SQL Server Integration Services.
1. Amazon.com 2. Bank of America 3. Capital One 4. Coca-Cola 5. Dell 6. E*TRADE 7. FedEx 8. Ford Motor Company 9. Google 10. Home Depot 11. IBM 12. Intel 13. JPMorgan Chase 14. Kraft Foods 15. Lockheed Martin 16. McDonald's 17. Microsoft 18. Morgan Stanley 19. Nike 20. Oracle 21. PepsiCo 22. Procter & Gamble 23. Prudential Financial 24. RBC Capital Markets 25. SAP 26. Siemens 27. Sony 28. Toyota 29. UnitedHealth Group 30. Visa 31. Walmart 32. Wells Fargo
| Author info | Rating | Review Summary |
|---|---|---|
| Tech Lead at a consultancy with 11-50 employees | 3.5 | I use SSIS mainly for reporting, finding it effective for streamlining processes with SQL-based data, though setup is initially complex. It could improve integration with Power BI and third-party tools, but overall, it meets my needs well. |
| Manager, Data Operations at a manufacturing company with 5,001-10,000 employees | 4.5 | I find SSIS highly reliable and easy to use for data integration, requiring minimal maintenance and offering strong compatibility with various platforms. Its usability is excellent, though logging could be improved. Overall, it delivers great efficiency and value. |
| Managing Director at Knights Innovation Support Centre | 4.0 | As a Microsoft Certified Trainer, I find SSIS valuable for handling large data in warehouses, though it lacks support and effective education. Stability is excellent, but the complexity could pose challenges without the right training or exposure. |
| Managing Partner at Dynamis Informatica | 4.0 | I use SSIS primarily for creating and fixing on-premises packages, moving data to the cloud, and preparing it for Power BI. Its integration with SQL Server makes it cost-effective, though it can be challenging for complex transformations. |
| Data Scientist/BI Developer at QNB Invest | 2.5 | I use SSIS for ETL processes in the EDW layer, but it has too many bugs, causing inconsistency in performance across different computers. I previously used Informatica, which was more reliable without as many bugs. |
| Head, Development Chapter (DevOps) at First Bank of Nigeria Ltd. | 4.0 | We use SSIS for ETL tasks, enabling data extraction from sources like Oracle and SQL Server for Power BI dashboards. Its data transformation capabilities are invaluable, though it struggles with large data volumes compared to Oracle, needing improvements in stability and efficiency. |
| Senior Systems Analyst at Optum | 4.0 | We use SSIS for ETL to efficiently move and translate data. It's highly scalable, integrates with multiple servers, and allows custom coding. However, it experiences bugs and lacks built-in API support, for which improved debugging tools would be beneficial. |
| Business Intelligence Architect at a financial services firm with 5,001-10,000 employees | 4.0 | In my SSIS experience, its package management and workflow flexibility are most valuable. While we've faced SQL Server performance challenges during updates, SSIS remains a reliable ETL tool, streamlining processes despite some Oracle integration and versioning issues. |
| Specialist Software Engineer at a financial services firm with 10,001+ employees | 3.0 | I primarily use SSIS for transferring data between application databases and OLAP systems. While it's easy to set up, SSIS struggles with large data volumes, causing frequent slowdowns. Azure Data Factory has proven to be a faster alternative. |
| Information Technology Division Director at Ethiopian Roads Administration | 4.5 | I previously used SSIS with SQL Server but have decommissioned it. Its performance is the most valuable feature, though I found the integration and user interface lacking. I haven't used any similar products or considered alternatives. |
My main use case for SSIS is reporting. I pull reports from warehouse management and various entities to ensure that everything aligns with the reports.
The main benefits SSIS provides for my company is to streamline processes. The reporting process is the most useful for me, as most of our data is captured into SQL, making it easier to pull the differences in reports for the year.
SSIS could be integrated with more services, such as Power BI, to make the reporting structures more user-friendly.
The initial setup for SSIS is somewhat complex in the beginning, but once you understand the processes, it becomes very simple.
SISS could support more third-party solutions because plugins tend to come into play when you get involved with other third-party items.
I have been working with SSIS for just over five years.
I would rate the stability of the product at an 8.
I would rate the scalability of SSIS at a 7 because we are able to use various third-party items with it, allowing for functionality with a number of different things.
I have to check with the team about technical support from Microsoft because we have not really needed to get any technical support for it.
I am not able to compare SSIS with a product from another vendor at this point. SSIS is a unique solution from Microsoft, and I have not really utilized anything else.
The initial setup for SSIS is somewhat complex in the beginning, but once you understand the processes, it becomes very simple.
Pricing is pretty reasonable, so I would rate it at a 5. However, it could be a bit cheaper.
When I talk about SQL Server, I am working with SSIS, the data integration tool. I am not entirely sure if I use SSIS as a library of transformations or if I personally work with an extensive library of transformations. I have integrated SSIS with SQL Server Management Studio, and I am very satisfied with the integration as it is integrated well. I am not using the debugging feature in SSIS because the developers would be the ones that would actually utilize it. I have noticed that in 2022, AI functionality has actually been implemented already. I would rate this review overall at a 7.

A lot of integration is my use case. We move data around and our teams that we support write integration packages to move data from one source to another source or to change data as needed.
Moving data makes things so much easier. We have a lot of data movement, and we create many data marts from sources, which allows us to create data marts very easily.
Its usability and ease of use are standout features. It is really easy to use - almost too easy at times. Users don't have to be experts to use their tool set and utilize the clicking mechanisms, drop down boxes, and other features to build a package and run it.
The configuration is very easy and the system is very stable. I would rate it at a 10 as it is highly reliable; we have never had any problems with it.
Very little maintenance is required on my side. While you need to keep the product up to date, the maintenance requirements are minimal.
SSIS integrates with all Microsoft tools seamlessly. We have used it against Oracle, DB2 and SQL. It integrates and can move data around from any data platforms, making it very diverse in that standpoint.
It is a very robust tool that can work with many data sources, and its main strength is that it is extremely easy to use.
The logging capabilities could be improved, particularly for error logging.
We actively use this solution.
We haven't had to use their support specifically for SSIS, but in general, Microsoft support rates at a seven or eight out of ten. They're not perfect. The first line of support needs to be more knowledgeable.
Positive
The return on investment has been very high. The tool has made us tremendously more efficient and saved us a significant amount of money, though I cannot put an exact figure on it.
It was included in our licensing for SQL server, and our licensing for SQL server was extremely cheap, making it a very good price point for us.
I am a leader, so I haven't used the technology as much as my teams do. I manage the infrastructure rather than write code, so I cannot speak to specific features or AI capabilities.
Our team's involvement was limited to installation, as a different group handled the actual usage of the tool. We don't have specific use cases to share.
On a scale of 1-10, this product rates a 9.

I work with all of them as a Microsoft Certified Trainer, particularly around the Business Intelligence SQL space. I tend to do quite a bit of work around the SSAS space, SSIS, SSRS, and integrating that into a lot of SharePoint and other spaces.
The challenge is building from the KPIs. Being able to put your KPIs in place starting with understanding a board of directors and their needs, and being able to build the KPIs for an organization from that level is important. Then being able to deliver those on a dashboard, such as Power BI, or something else, also matters. Additionally, being able to build cubes that allow for rapid analysis over a long period of time is crucial. The one thing which is missing often enough is building out your data warehouse with your data models, so helping to build the data models is very important. I appreciate how it handles large data in your warehouse.
Stability is rated at 10. One other important aspect I appreciate is that SSAS is included in the base installation of SQL Server. Obviously, it requires installation, but it is readily available, which is a major strength. It's all about setting it up, configuring it, and then using it. If there are additional costs associated with it or separating it as a second product, that would be a disadvantage.
The area of improvement is really in education. Microsoft is trying to push everything as a Power BI solution or trying to get people to solve the problems which are solved with SSAS in another space in Power BI, or in Power Pivot, is not enough. There's not enough marketing, conversation, and support around that space. As a result, we end up with people not understanding that you need to build your models correctly, and then they try to model everything inside of Power BI, or another visualization tool, without first building the data model.
That leads people to consider alternate solutions because SAP and others argue that their whole thing is in memory, and they disseminate misleading information. Additionally, what would be very helpful is local user group developments, so getting people around the table and teaching them how to use it. That is the biggest problem; it's not the technology itself. The challenge lies in Microsoft withdrawing a lot of the qualifications and watering down its emphasis, leading to a perception that this is supposed to be an elite product.
There's no support for it at all. If you haven't undergone the qualifications, you wouldn't even know you should phone someone. If you are aware that you can, you might have to talk to a provider. Within the South African context, if you are getting your enterprise agreement from First Technology, they don't provide support; they prefer doing the work for you without proper telephonic support. The support rating is a one.
SSAS was introduced in SQL 2008 as a starting point and I've been using it since then.
It is stable and reliable.
It's a highly scalable solution.
The initial setup of SSIS was really laid out in the 6234 course. However, if you were to discover it on your own, it can be complex. There is a model selection that needs to occur, which isn't obvious. Also, considering that T-SQL is Microsoft's own proprietary version of the SQL standards, someone familiar with Oracle or SAP wouldn't have an easy time grasping analysis services. Those who use analysis services do so because they were correctly introduced to it. For me, it wasn't complex because I'm a Microsoft Certified Trainer and was exposed to it; those I taught didn't find it complex either due to the right material. But for someone unacquainted with the space, the journey is longer, leading to different results.
I have opted in to share feedback about working with IT solutions. The overall rating for this solution is 8 out of 10.

Neutral

I use SSIS for data loading ETL processes. I am responsible for the EDW layer and get new data from other data sources into the EDW via SSIS.
SSIS has too many bugs. Sometimes it works, sometimes it doesn't. I try to use a package, and it won't work on my computer, but it will on another user's computer. If I could rely on the program more, it would be better.
I have used SSIS for approximately two and a half years.
SSIS is not stable.
I am unsure about how easily it can expand to meet our needs, or the scalability of SSIS.
I am not in contact with Microsoft right now, so I do not know about their technical support.
Neutral
Before SSIS, I used Informatica. Informatica did not have as many bugs as SSIS.
The setup is easy to use and understand.
Everything is done in-house in my company.
I would not recommend SSIS to other people because there are too many bugs, and it is unstable.
I'd rate the solution five out of ten.

We use SSIS for data extraction, transformation, and loading processes. This includes extracting data from various sources like Oracle and SQL Server, and then transforming it for use in reporting tools like Power BI dashboards. While we haven't directly migrated data between databases using SSIS, we have used it extensively for ETL tasks, such as extracting data for analysis and reporting purposes.
Improvement as per customer requirements.
I have been using SSIS for the past 10 years.
In terms of stability, SSIS is reliable and easy to use compared to other solutions.
For SSIS deployment and maintenance, we have a team of around five technical staff members, including engineers and managers.
I'm not involved in licensing details, but SSIS provides value to our organization by simplifying data management tasks.
When comparing SSIS to other ETL tools, I find SSIS to be user-friendly but less efficient in handling large volumes of data compared to Oracle. SSIS could improve in managing higher volumes of data and enhancing stability, especially for data sets exceeding two terabytes. The enhnacemnets in indexing and data structure retrieval would be beneficial for managing data more effectively.
I'd rate SSIS an 8 out of 10 for its overall performance. I would recommend SSIS for its ease of use. Whether you're a beginner or experienced, it's intuitive and allows for easy development of logic and infrastructure.
We use the solution for ETL. It helps to move data from one server to another and translate it in the middle.
I like that this solution is very scalable, accommodating large datasets and various types of servers. It integrates with most common database servers and allows for customization through coding, including complex scripts. Compared to Alteryx Designer, SSIS offers more customization. Its data cleaning capabilities are highly accurate because we can run tests as data is loaded, ensuring it meets all requirements before reaching the final destination. The ability to write custom SQL and C# code within SSIS packages is its greatest feature.
SSIS has room for improvement, mainly because the overall package can be buggy. It often locks up, requiring a restart, which is annoying. However, since it's free, we tolerate these performance issues. I'd like to see better debugging tools in future releases and improvements in API calls; It would be helpful if SSIS had a built-in API engine so we wouldn't have to rely solely on database connections.
I have been using the product for 15 years.
Regarding capability, SSIS is very scalable, handling small and large datasets.
Support from Microsoft can be expensive.
The solution's deployment is complicated since we need an admin or DBA to install it. The deployment process for SSIS is straightforward and quick. You select the server and deploy the package. It usually requires just one system administrator to deploy, with the necessary system rights to access the server. We create change requests, and the package is deployed accordingly.
The tool's deployment can be done in-house.
The solution comes free of cost.
You need to be patient with the bugs and restart frequently. I rate the solution an eight out of ten.

In my experience with SSIS, I have found its most valuable features to be its package management capabilities and the flexibility it offers in designing workflows. We often use templates, inheriting and embedding scales in SSAS to streamline our processes.
In upgrading SSIS, we encountered challenges fixing SQL Server and performance issues, including problems during a failover in our data warehouse. After resolving these issues and conducting load balancing tests, we proceeded with the SSIS upgrade, anticipating potential complications.
I have been working with SSIS for almost ten years.
I would rate the stability of SSIS at a solid nine out of ten. While there may be occasional encounters with bugs or performance issues, personally, we haven't faced significant problems in our usage.
I would recommend SSIS for both smaller and larger companies. We operate as a small to medium-sized enterprise with a considerable volume of data, around 30 to 40 terabytes in our data warehouse. Despite being an SME, SSIS has proven effective in handling our ETL processes seamlessly. If an organization has a similar data size, around the 30 to 40-terabyte range, SSIS can be a suitable and reliable choice for managing their data integration needs.
Microsoft's technical support has been good, especially for critical issues in a financial institution like a bank. The bank receives strong support from Microsoft, and there is a significant level of accountability. If any issues arise, particularly those impacting financial operations, Microsoft is obligated to address and resolve them promptly.
While executing tasks and managing data flow, we occasionally encounter Oracle system integration, and in the past, we have used Antunica, though it seems Microsoft's support for it has dwindled in recent years. Despite some versioning challenges, our workflow design, execution, and deployment have been relatively smooth using SSIS.
SSIS implementation has been straightforward for us, using scheduled tools like Kubernetes for deployment and master packages in SSIS. It seamlessly integrates with Microsoft products and other databases like Oracle or Teradata. We haven't faced issues integrating with third-party solutions, and even with tools like Attunity, it has worked reliably for almost a decade without performance problems.
The pricing of SSIS is generally considered reasonable in comparison to other data integration tools in the market. In terms of licensing, I find Microsoft's pricing policy generally favorable, especially when comparing it to other products like Power BI. Microsoft's pricing is competitive, and they seem to have a good strategy, as evident in the success of Power BI. Over the years, SSIS has gained recognition, and Microsoft's promotion efforts have been effective.
If you are considering alternatives to SSIS, I have worked with ODI in the past during consulting engagements. Colleagues have praised Informatica as a superior solution to ODI and SSIS, though I'm not aware of its pricing. While SSIS is lauded for its simplicity, there might be disadvantages compared to competitors like Informatica. However, our data warehouse team is highly satisfied with SSIS, and it is widely used in the industry. It is a common and reliable ETL tool with easily accessible solutions through internal resources and online searches, making problem-solving straightforward.
For those interested in SSIS, my advice is to go for it because it is a simple and effective solution. Even without deep knowledge, there are ample resources, including comprehensive documentation from Microsoft. Exploring their documentation provides access to numerous samples and best practices, making it user-friendly, especially for developers. So, don't hesitate to leverage the available materials and give it a try. Overall, I would rate SSIS as an eight out of ten.

We primarily use the solution for getting the data from the application database and to the OLAP system. We extract the data from OLAP system and build data warehouses. Basically, this solution is used to build OLAP.
This tool works well when users aren't working with large amounts of data.
It is easy to set up the solution.
SSIS is very, very, very slow. It hangs a lot of the time. There is a buffer issue and a memory issue.
You need to keep a lot of packages. There's a lot of maintenance.
The design is not user-friendly.
They need to include a lot of connectors, and their component should be much faster. The component, transformation component, like lookup datatype conversion, doesn't work well for large amounts of data.
I've been using the solution for two and a half years. I've used it for a while.
It is quite stable. It's safe and reliable. A lot of organizations are using it instead of Azure Cloud.
I'd rate the scalability four out of ten. The solution does not handle large amounts of data well. Azure Data Factory is much, much more scalable.
We've also used Azure Data Factory, which is much faster than SSIS.
The initial setup is not difficult. However, when the volume increases, it slows down. It's a bit of an obsolete tech stack and is not very current.
You only need one person the setup and deploy the product.
We handled the initial setup in-house. We did not need outside assistance when handling the setup.
I'm not aware of the exact pricing. It's being handled by another team.
We're using Visual Studio 2019 and SQL Server Integration Services 3.16.
I'd advise potential users to go and learn Azure and use that. Use Data Factory, not SSIS.
I'd rate the solution six out of ten.
Presently, we have decommissioned the solution. Earlier, we used SSIS with the SQL Server.
The most valuable feature of the solution is performance. It works by connecting to the SQL Server.
Integration and the user interface are areas with certain shortcomings that require some improvements.
I have been using SSIS for more than fifteen years.
Stability-wise, I rate the solution an eight out of ten.
It is not a scalable solution. You have to replace it.
There were five users of the tools in my company.
I have never contacted the solution's technical support team.
I have not used any other product that is similar to SSIS.
Some experts need to be involved in the deployment process, which is straightforward and easy to manage.
The product's setup phase was straightforward.
The product's deployment phase was easy.
People have to opt for a perpetual-based licensing model.
It can be useful for data integration across different sources since it is a stable product.
In terms of a complex data transformation process you've managed, the tool offers some accesses associated with integration services.
The data warehousing capabilities of the tool benefited our company, and it is one of the good things about the solution because there are different databases that you can access throughout the process to collect information as you desire.
Our company can recommend the tool depending on the client's requirements. We are using it for data warehousing and collecting some information from the database. Nowadays, there are probably different solutions that can do that efficiently and effectively.
The debugging and error handling capabilities of the tool improves our company's data integration task but it is very challenging. The people who use the tool to work have mentioned that debugging issue is a bit difficult for them.
I think it would be better if people could check out other solutions available in the market and compare them to SSIS.
I rate the tool a seven out of ten.