SSIS Reviews

We are using it in our company and for our clients. I have experience in working with the whole data cycle, which includes data collection, transformation, and visualization. I have worked with the end-to-end process, and I have handled data integration, analysis, and visualization.

I specialize in Microsoft tools, and I have used SSIS for data integration and Power BI for data visualization. I have also worked with Tableau for data visualization and Talend for data integration.

The most valuable thing is that it is easy to connect with Microsoft tools. In Europe, particularly in France, a lot of companies use Excel, SQL Server, and other Microsoft tools, and it is easier to connect SSIS with Microsoft tools than other products.

It is also easy to learn and user-friendly. Microsoft is also good in terms of technical support. They have built a large community all over the world.

When I compare Talend and SSIS, Talend provides more features. With Talend, we can handle a large volume of data. Talend is usually used to treat a large volume of data, which makes it better than SSIS on the data side. 

Talend also has a very good Talend Management Console to schedule the jobs and do other things. It can also be easily connected to version control tools such as GitHub or SVN. The last time I used SSIS, it was connected through TSS for the Windows Console version. I am not sure it has been improved or not. If it is not improved, Microsoft should improve it. They should change the product to provide another console. 

Microsoft is good in terms of technical support. They provide 24-hour support. They have built a large community all over the world, and one can find easily the answer to an issue or problem by searching on the web.

Its installation wasn't my job. We have a team that specializes in infrastructure, and they install and set up the tool. When I was a student, I used to install it myself, and it wasn't really difficult, but I have not installed it on a professional site or for a company. 

Based on my experience and understanding, Talend comes out to be a little bit expensive as compared to SSIS. The average cost of having Talend with Talend Management Console is around 72K per region, which is much higher than SSIS.

SSIS works very well with Microsoft technologies, and if you have Microsoft technologies, it is not really expensive to have SSIS. If you have SQL Server, SSIS is free.

I would rate SSIS a six out of ten. I prefer Talend over SSIS.

It's too early to say how it has improved my organization, as we've just begun using the solution. First, we need to create the appropriate role before we see organizational improvements. We're just in the discovery phase of the tool.

I couldn't point out a specific feature above all others, but I can say the solution is very useful to us. It's well designed and quite straightforward. There isn't much of a learning curve involved. It's a well-documented solution. 

It's at a very early stage in terms of adopting the tool, so I can't speak to if there are areas for improvement just yet.

Video training would be a helpful addition, however.

The stability of the solution is impressive.

The scalability of SSIS is very good. Right now, only I am using the solution, but we plan to increase usage in the future.

I haven't required any technical support, so I'm not in a position to judge it.

The setup is straightforward. It's very easy to install.

We did the implementation ourselves.

We did not evaluate other options before choosing this solution.

We are just beginning development with this solution, so we're currently starting with the on-premises version.

So far, I haven't been disappointed by the tool. I have not explored the dashboard tuning feature yet, so I don't know if there are things we can do, like building our own matrixes or choosing deployment preferences, but I hope that will be the case.

I'd rate the solution ten out of ten.

We primarily use the solution for data transformation.

The most valuable features for our company are the flexibility and the quick turn around time in producing simple ETL solutions. Also, the use of the configuration on Azure. Our clients are basically secret sever based, so it works well there.

In terms of improvements to the solution, I don't think I have that expertise on it to recommend product enhancements right now. I've only used a few parts of it. Based on what I've used so far, I am happy with it.

I come from a coding background and this tool is graphically based. Sometimes I think it's cumbersome to do mapping graphically. If there was a way to provide a simple script, it would be helpful and make it easier to use.

The solution is currently running in production. It's stable.

We've never had to contact technical support. We generally handle any issues ourselves.

The initial setup is straightforward. Deployment is done by another team. I download the package and deliver it to them and they deploy it onto the cloud. In terms of maintenance, we only need one person.

We are using the 2014 Public Cloud version of the solution, under Microsoft Azure.

In terms of recommending the solution, it obviously depends on the level users you have. If you mainly have a simple graphical based user then maybe you could go for SSIS. If you want to take control of the whole ETL process, you should look for another tool. I use Informatica PowerCenter as well. That's a bit more of a robust ETL solution.

I would rate the solution at six out of ten.

Movement of data and creation of files. ALl the typical things that you would have a ETL solution do. Data movements were in the millions and no calculations were completed. This means it was always a select * from where ever it was coming from and going to. Light translations like concatenation was being used. 

SSIS was easily adaptable to our group. It was cheaper than the other tools that we compared it to, however I feel that we got what we paid for.

The packaging and how it is organized is good for someone that really has never seen ETL before. 

Scalability of SSIS needs some improvement. Seems to get sluggish as soon as we hit a high volume of data.

Again it failed a lot and by a lot I mean every day. The failures were false alarms and caused many sleepless night for our company that I used to work for.

SSIS is good for smaller shops that don't really have a high volume of data.

I would rate the customer service as poor. 

We were using Hyperion Application Link. We switched because HAL was being sunset.

Never participated in the initial setup.

In-house.

For the money, it's a decent tool. However, if the budget was larger I would have gone with a different tool

Look at how this product is sold to you. Ask yourself, am I getting everything that I need. Its more expensive to get the additional adapters after the fact.

We looked at ODI, Informatica, and DataStage. All three we had in-house. ODI was the better option and after dealing with SSIS for only a few months, we ended up using ODI.

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 the solution for integration packages for ETL in order to build data warehouses.

The workflow features have been very valuable. You can have automated workflows and all the steps are controlled. The workflow functionality of integration services is excellent.

The solution should offer more information online for users of SSIS. There are only a few general data sources available, but it would be helpful if there was more extensive information.

The solution could also use some more intelligent discs for data manipulation, or maybe some artificial intelligence as well. It needs more integration tools, so you can connect to different sources.

The solution is quite stable.

The solution is very scalable. The amount of people that use SSIS from our end depends on the project, so it varies. We increase the usage of this product based on the projects that we get. Basically, each project that we do, we use this solution for integration purposes.

Technical support is quite good.

I've always used SSIS. We never considered any other solution. We might have used some tools that were developed in-house occasionally, but by and large, we always use SSIS.

The initial setup was straightforward.

We use the on-premises version of the solution.

I would recommend the solution to others. I'd give it a rating of eight out of ten.

We use this solution for ETL, which includes data summation and cleaning. 

This solution used in an on-premise deployment, for now.

I have used most of the standard SQL features, but the ones that stand out are the Data Flows and Bulk Import.

The synchronous processing needs to be improved. For batch processing, it works fine, but when you start to do real-time processing, I find that this solution is not strong, depending on how you use it. If you use it for short batches, micro batching, that might work, but it is not as good for queuing real-time processing. This solution needs full support for real-time processing.

The solution needs better support for XML and JSON.

I use this product extensively, on a daily basis. It is stable.

Over time, I think we'll most likely start to decrease usage. This will happen as we move to more real-time processing, and we will most likely start to do more queue processing. In terms of batch processing, it will scale down considerably.

In the catalog, it's supposed to be scalable. I think that it has support for an SQL cluster.

In my opinion, I think it's a bit more limited in terms of scalability, although it scales with the database. I would say that the scalability is intermediate in terms of being able to launch multiple instances, or it could do load balancing as well. I think that would be a bit more challenging.

We haven't needed to contact Microsoft technical support. When we have trouble we usually use Google to search for what we need to find out. Also, in terms of issues, there's a lot of information on SQLServerCentral and Stack Overflow.

For the most part, we started with this solution. 

The initial setup of this solution is pretty much straightforward.

If you want to develop with Visual Studio then you have to install the data service add-ons afterward, so it is a bit cumbersome. Then, if you want to use the catalog on the database, with deployment there are often security issues and you have to get an SQL catalog up and running. This can also be a bit cumbersome.

I would say that it takes a day or two to deploy this solution in a new environment, and it can be completed by one or two people. A single developer may be sufficient to deploy and maintain the system.

I implemented some of this myself and had help in terms of setting up the security. There are often security settings that require the assistance of a DBA.

This solution was already in place. That's what is available and it's what people know. Going forward, this will most likely change.

My advice to anybody implementing this solution is to look into whether to use it on a catalog in a database, versus using package deployment. There are pros and cons to both approaches in terms of deployment and security. I would say that's something that needs to be evaluated quite early. There are lots of benefits to the catalog, but also a bit more admin attached to it.

Another consideration is real-time processing needs. If this is a requirement then I would recommend against using this solution, unless the next version has a new set of features specifically for real-time processing.

I would rate this solution an eight out of ten.

Some of the valuable features I have found with this solution has been the variety of transformations that are possible and it works well with SQL servers. The majority of our clients that I worked for, their whole systems of data is using SQL server which has worked better for them.

The script component is very powerful, things that you cannot normally do, is feasible through C#. If you can write a script you can import it through the Script Task.

The solution could improve on integrating with other types of data sources. We had issues with connecting to Oracle, it did not do as good of a job as it did with SQL servers. 

In my experience, more efficiency is needed when it comes to dealing with huge volumes of data. However, this is also dependant on the server capacity.

In an upcoming release, they should update the features to facilitate efficient data transfers. 

I have been using the solution for approximately 10 years.

We have not experienced any behavioural differences with the operations of the solution, it is stable.

We typically implement the solution for enterprise-size companies.

The installation was easy.

It would be beneficial if the solution had a less costly cloud offering.

Informatica and Talent, are two options I am currently evaluating.

Customers have moved on pass SSIS and use Azure Data Factory, Databricks or something similar. We have a few of our customers looking to moving on to Informatica or Talent. This is how I was led to itcentralstation.com, to learn more about SSIS and how it was compared to Informatica. 

I have never had a situation where a particular transformation was not possible in SSIS. We have always been able to meet the demands of our need with SSIS.

I rate SSIS an eight out of ten.