SSIS Reviews

We use the product sometimes to implement some ETL processes.

We have to transform some data from students so that we can help to make some decisions on what we call deterioration. We receive a lot of data from the government, and sometimes we have to split it into several parts as it is a huge amount of data. We have to put it in a standardized way. We use the solution as a product. It is one of the use cases that we do. When we have other systems, like for staff to control, we also use SSIS since it's appropriate to our system, and we need to put it in certain ways so that we can read it and manage it. 

It is the most valuable for staff processes in order to gain efficiency. It allows us to get the data normalized easily.

The solution is stable.

It can scale well.

The deployment process is very easy and quite quick.

They have good documentation. 

We'd like them to develop data exploration more. 

The support could be better.

I've been using the solution for more than five years. 

The solution is stable. We haven't had any issues with that. If we need more processing power, we can increase the resources of the machines below it. 

The scalability is good.

We do not have a lot of users. The processes we do have run at night.

It's not about how many users use the solution, it's about how many people benefit from it. There are many that benefit from the output.

I've never used technical support. Microsoft does have a very good document library, however, if you have an issue and need support, it can take a very long time to get help.

Neutral

How easy or difficult the setup is depends on the size of the process that we want to normalize. If it is a big ETL, it's not always that fast. We are considering changing to a different platform so that it's easier. For example, we are looking into SQL to have another kind of data exploration.

The first time we initially set it up, it was quite fast. The deployment of the integration services for the very first time without any process implemented took about a day.

We handled the setup internally. We did not have to worry about dealing with any consultants or integrators. 

We have yearly licensing.

We are currently looking into SQL to see if it would be easier to use. 

We already have an enterprise contract with Microsoft. We didn't want to spend money on other solutions.

We still have a few versions running. The one that we use the most is the 2017 version.

I'd recommend the solution to others. I'd rate it seven out of ten.

If you are deploying a data strategy for your company, you need more than SSIS. If you need to go fast and implement some ETL processes with no help, it's quite easy to do and learn.

I have been using SSIS for approximately six years.

SSIS is stable, but extensive ETL data processing can have some performance issues.

The scalability of SSIS is good.

We have approximately 10 users using this solution in my company.

I have not used the support from SSIS.

The initial setup of SSIS is easy.

I rate the initial setup of SSIS a five out of five.

We purchased the standard edition of SQL Server and SSIS came with it free of charge.

My advice to others that want to implement SSIS is they should watch a video or a tutorial for eight hours to implement a project for ETL. If you would like to migrate to SSIS, and link to the data sources, it will take approximately 30 minutes to watch a video tutorial on YouTube. You can search for the topic you are wanting to do, and you'll find the solution. There is a huge community to find the tutorials you need.

I rate SSIS an eight out of ten.

The one internally also developed some applications for some specific problems. For that use case, we are using the solution for different purposes, for example, for integration between data disks to databases, as well as for the application level side of integration. We are using the SSIS service actually. And we also have different expertise on the database level. We're also using it for different scenarios. We use it with Microsoft products. It's a part of our strategy, in the data aspect.

The performance is good.

It's easy to use. 

The visibility is great.

We have found the solution to be very straightforward to set up.

The solution is stable.

It can scale well. 

Microsoft should offer an on-premises support warranty for those using that deployment. They seem to be withdrawing from on-premises options. 

I've been using the solution for ten years or more.

The solution is stable and reliable. The performance is good. There are no bugs or glitches. It doesn't crash or freeze. For us, it's worked quite well.

The solution is scalable. It's not a problem to expand. 

Currently, we are using it in the development environment, so we have around five users.

Increasing usage depends on the structure that we have. Let's say if the organization plans to increase the structure and the developer number, we might increase usage a bit. For the time being, five is enough.

The good thing with Microsoft is you can have support online even without engaging directly with Microsoft. Things are very cloud sensitive. You can also request help from the vendor. Less than two years ago, in 2021, Microsoft stopped offering assistance to those using the on-prem solution.

However, in those cases, you can still find support and answers online, from different users' experiences. There's lots of information out there about Microsoft. It's not hard to get help and find answers. 

Positive

I'm not sure what we used ten to 12 years ago. It has been a long time since we started using this particular solution. 

The solution is straightforward and simple. It's not overly complex or difficult. It's actually quite easy for us to get everything up and running. We can finalize everything within a day. It doesn't take a lot of time to implement it. 

One person is enough to deploy and maintain the solution. That said, it depends on an organization's planning strategy. It might not take a lot to do that kind of activity.

Usually, we handle the setup in-house. However, we have in the past had the help of a consultant or using a supplier. 

With the cloud deployment, you can get a three or five-year license. You may not be able to get an on-premises version anymore. 

I've used the 2014, 2016, and 2019 versions of the product.

I'd recommend the solution to others.

I would recommend the solution to others.

Overall, I can rate the solution an eight out of ten. We're pretty happy with it.

Our company sells contracts when you buy a car. We sell aftermarket insurance for the tyre, wheel, ding, dent, windshield, etc. When somebody buys a contract, we capture all of that data into a legacy database PostgreSQL, and my task is to incorporate that into our financial platform using T-SQL. So, I write queries, procedures, and views. I use SSIS, and I use SSRS. My job is to get the data into our financial system so that we can process claims, payments, cancellations, and refunds.

It's something I needed for bulk imports. I'm not a big fan of it, but I haven't seen anything better.

One of the problems I ran into was that the database that I had had a status. I couldn't always flip the status, so I didn't know what data I already had. I had to use SSIS to grab a bunch of data and check the database to see if I needed to insert it. It works okay, but as I plan better, I'm trying to weed it out. SSIS is a bit prickly because anytime you go and change something, it tends to break. That's because there is metadata behind the tool.

I have a tool called ZappySys. I need that tool to cut down on the complexity of SSIS. That tool really helps with a quick turnaround. I can do things quickly, and I can do things accurately. I can get better reporting on errors.

I'm not a fan of SSIS itself. I would rate out-of-the-box SSIS a four out of 10, but with the ZappySys tool, it is a pretty good solution, and then I would rate it an eight out of 10.

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.

I use this solution to create BI reports. I have used SSIS in more than twenty projects over the past six years.

There are many good features in this solution including the data fields, database integration, support for SQL views, and the lookups for matching information.

I have had problems in the past with this tool. The debugging could be improved because when it came to solving the errors that I've experienced in the past, I've had to look at the documentation for more information.

The main difficulty that I have had is to match different data types, where there were errors that I could not fix.

I would like to see better integration with the control sources. 

I am satisfied with the technical support for this solution.

The initial setup of this solution is quite simple.

We handled the installation of this solution in-house.

Overall, I am quite satisfied with this product.

I would rate this solution an eight out of ten.

This product is always used in projects because I'm in a company that develops software for other companies and we accept this type of work like programming and developing data models and writing the script for organizations to transfer their data between databases. We usually use these tools, and it's a cheap tool for us.

Usually, when I want to import data from other databases I use this solution. It's been about fifteen years that I've worked with an SQL server, and I'm a software developer. I've had many companies with different databases, and it's ranged from FoxPro, EDX and Oracle, and some other databases. When I want to import data I usually use this tool for importing data from the other databases to the server. It is really good, and it's solved many problems for me because I can choose the source table, destination table, source field, and destination field. I can match these things, I can write some queries to do this and because of that, I use this tool.

Sometimes when we want to publish to other types of databases it's not easy to publish to those databases. For example, the Jet Database Engine. Before the SSIS supported Jet Database Engine but nowadays it doesn't support the Jet Database Engine. We connect to many databases such as Access database, SparkPros databases and the other types of databases using Jet Database Engines and SSIS now doesn't seem to support it in our databases.

In future releases, it would be helpful to support new SQL databases. It would also be helpful if there was a way to use SQL with other languages like Python or ASP.NET.

The stability is very good and I recommend it to my friends, my coworkers, and the other companies.

The solution is scalable.

The initial setup was very easy for us and very good.

I installed the solution by myself.

The price is important to us. We are based in Iran, and we look for products with a good price because of the sanctions. Some other products such as Oracle are expensive here and we do not recommend these products to our customers. They are expensive and they are very difficult to work with them. They are very difficult and very complicated but Microsoft products are not like that.

I used this product when I was a student so I chose this technology because I understood it best. 

We chose the solution because we have some data in Oracle and we wanted to extract it and load the data into SQL Server. 

The type of port, like SSIS, I always recommend other companies to use it and other Microsoft products because they are very easy to use. There are very handy tools. It's very user-friendly and has a good dashboard.

I would rate the solution nine 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.