SSIS Reviews

We are a software development company and implement solutions like SQL Server SSIS for our clients. We do not use this product ourselves in the company but have experience with it because our client asked for it.

Our clients use it to transform data and generate reports. The use cases are generally simple, and not advanced or complex.

The interface is very user-friendly.

It runs a little bit slowly, although this may be because of our laptops.

I would like to see better integration with Power BI.

The stability is okay. It is easy to support.

There are approximately 10 users. At this time, there are no plans to increase usage.

I have not used technical support. Instead, I read blogs and the support that is available online.

The initial setup is easy, and we did not find it complex.

Our in-house team was responsible for deployment.

I would rate this solution an eight out of ten.

We use this solution to ingest data to a data lake that is built on SQL Server.

SSIS seems easy to use, is freely available for programmers to learn on their own, and has a lot of resources on the web for any trouble you get into.

The most valuable features of this solution are the fast insert and fuzzy logic matching.

This may be done, but upgrades to new versions required re-implementing each package.  This is worse for us because we have about one thousand SSIS packages. Hopefully they are now allowing backwards compatibility.

Generic processes should be used instead of custom code for each table.

Our primary use for this solution is to move data between points and applications.

This is a flexible tool to use and comes with the MSSQL server package.

This solution is easy to implement, has a wide variety of connectors, has support for Visual Basic, and supports the C language.

Tuning using this solution requires extensive expertise to improve performance.

This solution is included with the MSSQL server package.

We use this solution for extracting data from various databases and saving it in our data warehouse.

We use the on-premise deployment model.

My team is facing problems regarding the database connectors, which are not available. The MySQL connectors need to be purchased from outside vendors. They should provide connections for more SQL databases, free of charge.

The performance of this solution is not as good as other tools in the market. Compared to the same job is running in a different tool, it will take longer using SSIS.

This is a stable solution.

This solution is scalable.

The number of people I have using this solution depends on the size of the project. Normally, I need three to five ETL developers. Sometimes, if the project is big enough, then I will need more.

I have not contacted Microsoft Technical Support for this solution, although we have sometimes accessed the internet to research problems that we face.

In my previous company, I was leading a team who were working with Informatica. Here, they stick to Microsoft technologies and are unwilling to change.

The initial setup of this solution is very straightforward. In a few hours, everything was up and running.

The decision to use this particular solution includes many factors. Some companies do not want to purchase a license for another product because this one comes included with the database.

SSIS worked well for small or medium-sized Projects. For larger projects with huge data, I believe that you should search for another solution as you will need to do manual fine tuning. Additionally, some components such as SCD will show unexpected errors with huge data.

 As Microsoft is very slow in providing updates and enhancements to SSIS, I see that the future for Integration projects in Saudi Arabia goes towards other vendors products such as  Informatica powercenter, IBM DataStage, and Oracle ODI. 

Compared to other Integration tools, I would rate it a six out of ten.

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.

I'm using the solution primarily for e-memory and e-database calculation, mostly data blending (ETL) and massive table joining, etc. I also use it for data preparation and modeling.

With this solution, there is the potential to expand so that you can immediately write code onto the SQL server. Auto-parallelization is also critical for us. It decides automatically how many parallel sessions you have to run to get your query handled. You don't need to take care of any code, which is ideal. It's also highly scalable.  

The solution should work on the GPU, graphical processing unit. There should also be a piping integration available.

The design of the dashboard isn't great, visually, but the solution works, so this isn't so important to me.

SSIS's competitor, Autonomous Database by Oracle, offers you, depending on the performance of the server, new hardware, should you update your software. It advises you on how to optimize your system. It's AI and works as an artificial database manager. Microsoft doesn't have anything like this yet, but it would be nice if they did.

The stability of the solution is perfect.

The solution is very scalable. We have approximately 25-30 users for the on-premises version, and our cloud version has around 5,000 users.

We don't ask for much from technical support. We utilize community information, and source answers via the internet or online user information. I do find that communicating with Oracle is much better.

We previously used Oracle as an integration tool, but it's much more expensive than Microsoft.

The initial setup was easy.

We had a consultant that assisted us with the implementation.

I use the private cloud as well as the on-premises version of the solution.

I would rate this solution eight out of ten. I would rate it higher if the solution offered full automation AI for database managing, setup and management, and scaling of the solution.

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 the on-prem version of this solution. Our primary use case of this solution is for integrated data on the SQL server. 

It has a drag and drop feature that makes it easy to use. It has a good user experience because it takes into account your most-used tools and they're lined up nicely so you can just drag and drop without looking too far. It also integrates nicely with Microsoft.

There are a lot of features that could make this solution better. 

There were some issues when we tried to connect it to data storage. It was a connection issue. There is also room for improvement in the underlying language. 

It is stable. 

From personal experience, I really can't comment on the scalability, but from what I've seen online, and what I heard from other people is that it scales quite nicely.

I haven't had to contact technical support. 

We previously used an in-house solution based on Oracle APEX.

The initial setup was straightforward.

We used a consultant for the integration.

We chose SSIS because it was a good financial decision. It was the most cost-effective option at the time. 

There are many projects for the company that I work for that requires implementation for a client. I started with it because I just wanted to learn about it, and I had the chance to use it because there was an opportunity that opened up to implement it.

If you have data needs and you are a small or medium enterprise this is a good solution. If you are an organization and you're not dealing with terabytes of data, but you still need to analyze data to make that decision, you should go with this solution.

I would rate it a 7.5 out of ten.