SSIS Reviews

We use SSIS for transformation and migration.

The most valuable feature of SSIS is that it can handle real complex transformations.

SSIS should be made a little bit more intuitive and user-friendly because it needs an expert-level person to work on it.

I have been using SSIS for more than 10 years.

SSIS is a stable solution.

SSIS is a scalable solution.

The solution's initial setup is easy, but you'd need expert-level knowledge to work on it.

Overall, I rate SSIS an eight out of ten.

I have used this solution for integrating SQL into life insurance projects.

The data reader is the most valuable feature. 

If something is working, and then it doesn't work after it goes live, that creates a big problem. This solution is a useful tool, but the stability is a problem.

I have been working with this solution for eight or nine months. 

We have a stability problem because when something works, it works one time. The next time, it doesn't work. We don't know what is causing that problem. 

The solution is scalable. In the current use case, we have about 25 users of the solution. 

I found the setup comparatively easy. Within a day, anybody can start using it. Two or three people are more than enough for deployment and maintenance. 

The solution is working fine and it is useful. The only problem is the stability. 

I rate this solution as a seven out of ten. 

We use SSIS to migrate from an old server to a new one and to add some services. 

Like most Microsoft products, SSIS is user-friendly and easy to use. 

Sometimes, there are compatibility issues with some features. From time to time, I also face issues when trying to migrate. If I misconfigure things when I use Snapshot, the migration will fail.It can take a long time to migrate huge amounts of data, so it would be nice if that could be faster. 

I have been using SSIS for less than two years.

If you want to scale SSIS, you might face performance issues. I'm not sure SSIS has robust scalability. 

I rate Microsoft support six out of 10. Interacting with Microsoft support is challenging because it takes a lot of time, and sometimes you need to repeat your issue over to different support engineers. It was easier to contact support in India because Microsoft had a local presence there, but getting support in Cameroon is difficult.  The response time is slower.

Neutral

Setting up SSIS is complex, and if you misconfigure something, you'll have problems during migration. I rate SSIS six out of 10 for ease of setup.

I have only used the free developer edition. 

I rate SSIS seven out of 10. This is the only product I've used so far, so I don't know how it compares to others. 

I am an ETL developer working as an information zone leader. We are an outsourcing company to our customers.

The most valuable feature of SSIS is that you can take data from other servers which are not MS SQL Server or Oracle. 

I would like to see SSIS improve the collection of data trail servers and reporting. Future releases should improve the data lineage, as it currently is not good.

I have been using SQL Server Integration Services for five years.

This solution is stable, but the performance is not good. I believe it can be improved. Informatica is better.

I have not been restricted by this solution.

Prior to using SSIS I used Informatica. I switched because my organization is using SSIS.

The initial setup of this solution is not complex. 

Most of the time we do the implementation in-house, however, we have used third parties in the past.

Our license with SSIS is annual.

If an organization has the money, I recommend they use Informatica. 

I would rate SSIS a seven out of 10 overall.

We are a solution provider and SSIS is one of the products that we implement for our clients. I work as an integrator and a data flow developer.

SSIS is primarily used as part of the data flow for loading data into the data warehouse and exchanging data between applications.

The most valuable feature is the data integration process. It includes helpful functions such as data mapping, creating a connection, and loading.

The performance and stability are good.

The security could be improved, as it is more important in our context.

I have been working with SQL Server Integration Services (SSIS) for six years.

The stability is good.

We have four customers that are using this product.

I have never been in contact with technical support.

It's easy to install and create the first flow.

We have an in-house team of four engineers for maintenance.

All of my clients have this product included as part of their Microsoft license.

In summary, this is a good product and I recommend it. For people that are working in a Microsoft environment with the SQL Server database, it's the most recommended tool.

I would rate this solution an eight out of ten.

We have data that needs to be migrated. There is also a scan inventory. We create web data, pull it, search it, and then find answers and report stakeholders. So for this process, we use the SSIS.

You can get data from any data source with SSIS and dump it to any outside source. It is helpful. Getting, extracting, converting, and dumping data doesn't require much effort because we can do everything in the user interface. You drag and drop, then give the required input. It's intuitive.

Sometimes we need to connect to AWS to get additional data sources, so we have to install some external LAN and not a regular RDBMS. We need external tools to connect. It would be great if SSIS included these tools. I'd also like some additional features for row indexing and data conversion. 

We've been using SSIS for about four and a half years. 

If you run SSIS from the local system, it will lag, but it will work properly if you host on the cloud somewhere. It's a headache every time you run this locally.

Almost 10 percent of our users work with SSIS. It's more than a hundred. 

We haven't had that many problems. I have interacted with Microsoft support for some things, but it was a few minor issues. And with the updated VPA, it has been clear. I was satisfied with the support. We don't need support for these types of issues. We don't need to contact the support team or stop our business. 

The initial setup is never a complex process because the interface is user-friendly. If you are working with complex situations, then it can get complicated. We have a DBA team to handle the deployment. We must follow a process to deploy, so we need to get approval whenever there is a change. It's not easy for us, but it's still good, and it doesn't take much time. 

SSIS is on the cheaper side. In terms of value for the money, rivals are offering more database formats and cost processing, so SQL is lagging somewhat. 

I rate SSIS eight out of 10. I recommend it. 

We primarily use SSIS to collect data from one system and transfer it to another.

The Classical ETL processing of data.

It's a competent product. You can do a lot of things with it and learn how to use it. You can't do modern things with it, but you can do legacy things with it.

It is an out-of-date product, that we shouldn't be using anymore, as it no longer has many positive aspects.

It is an old tool. We make an effort not to use it. It's a legacy tool, that is nearing the end of its useful life. There could be some good things but we try not to get into that.

We have selected to go with another tool. SSIS should not be used whatsoever anymore. There are new versions, that are cloud-based, which are much more improved and much more feature complete.

We have been working with SSIS for 15 years.

We are working with the latest version. It hasn't been updated for many years.

I would say it's both reliable and stable. It's been on the market for 20 years, so it's a very mature product.

There are limitations. I wouldn't say that it is easy to scale. You can scale it, but I wouldn't say it can easily be done.

We have eight people who use this solution in our company.

Support is available, but it is no longer up to date. It needs to be improved.

We switched to Data Factory, which is the cloud version of SSIS and the primary reason for the switch.

Absolutely, the initial setup is a simple process. In my opinion, it's easy.

SSIS doesn't require any maintenance.

The deployment was completed internally.

It comes bundled with other solutions, which makes it difficult to get the price on the specific product.

It's actually a tool that we're attempting to eliminate. That should not be used. It's an old piece of equipment. That should not be used in any way.

If I was asked five or six years ago, I would recommend this solution, but not anymore.

I would rate SSIS an eight out of ten.

We have used SSIS in many ways. Primarily, it has been used for building ETLs for populating data warehouse and staging areas. We have developed a number of data marts that were populated. We build data migration packages, which have been reused a number of times with minimal configurations. Additionally, we build complex data integrations solutions and data hand-offs between different applications. We have even used it for creating and parsing SWIFT messages for data integration purposes. We also used it for email triggers. 

Now SSIS has introduced Big Data and cloud components. Though we haven't used any of these yet but it's really a very good addition to enhance SSIS capabilities.

SSIS is a tool which anybody can learn in no time. When we started the project, the whole team learnt it in one week's time and then were ready to start on project tasks. It gives you control. Recently, we used SSIS for a compliance project where we performed data cleansing and extensive data transformations to prepare data files for use of compliance (Trade Based AML solutions) application.

Script task and Script component for custom tasks: It gives you power to build your own logic if your requirements are not being fulfilled with existing available components. While the big thing is you can build your own components, that is not so straightforward. 

It's visual design interface is good and you can easily understand the flow. 

The debugging capabilities are great, particularly during data flow execution. You can look into the data and see what's going on in the pipeline. It has good logging capabilities as well.

It should have other programming languages supported as well from a scripting perspective. Currently, only C# and VB.NET are supported, which limits it to .NET. It should have Java support as well. 

We couldn't explore big data related components, and this area should be up to the mark, if not already. Certain data quality checks should also be part of it. Currently, this is the biggest area that should be looked into. Data quality is an essential part of the integration process and ETL. Currently, only the data profiling task is there. 

As an update, now SSIS offers big data components as well. 

5+ years.

I've been using it for last 7 years in different projects for different banks. Didn't face any stability issues yet.

Yes. It's very much scalable, but it all depends on how you design your solution. SSIS provides you extensive features and toolkit to handle all sort of data problems.

I also used Oracle Data Integrator as an ETL tool but it all depends on your need and customer preference. SSIS is being easy to use and things can be developed very quickly so I prefer to use SSIS for most of my data related tasks.

Its setup is very easy. You don't need too many components to start building ETL tools. Plus, there are a lot of online learning available for this tool. It can be deployed on any Windows machine with minimal requirements.

If you have SQL Server License then you can use SSIS without any additional cost.

Overall, we remained in a good position and in control while using SSIS. We didn't face any challenges.