SSIS Reviews

The solution is a business application. It's used for integrations between different databases, migrating from one to one, and importing data from one thing to something else.

Overall, it works well. 

The performance is good.

It's saved time using visualization descriptions. 

The initial setup is straightforward. 

The product is scalable.

It's stable. 

We find the solution to be reasonable. 

We have faced some problems, mostly from a different provider with different language handling.

We'd like the solution to increase the types of integrations on offer. We'd like more integration capabilities. 

I've been using the solution for 20 years. 

It's very stable and reliable. There aren't bugs or glitches. It doesn't crash or freeze. The performance is fine. 

We can scale the solution just fine. 

It is our plan to increase usage in the future. 

We have ten users on the solution right now.

I've never used technical support. I cannot speak to how helpful or responsive they would be if we needed assistance. 

We did not previously use another solution. 

The solution is straightforward to set up. It's not overly complex. It takes about half an hour to set up.

We have five people that can handle deployment or maintenance tasks. 

We can handle the initial setup on our own. We do not need outside assistance from integrators or consultants. 

The solution is fairly priced. I'd rate it four out of five in terms of affordability.

My company is a Microsoft partner, and we use multiple Micorosft products.

We're using the latest version of the solution. 

I'd recommend the solution to other users and companies. 

I'd rate the solution eight out of ten.

We use this solution as an ETL tool to move large volumes of data from one server to another.

We like that this solution includes a developer edition, free of charge, to allow for training.

This solution is a free, additional feature with an SQL database license, which we appreciate.

We would like the solution to be expanded so that it is available for other platforms than just Microsoft.

We would also like to see this product improved so that the the tool can handle streaming data, and near real-time data capture.

We have been using this solution for more than 20 years.

This is a very stable and dependable solution.

We have found this to be an easily scalable solution.

The initial setup of this solution was very straightforward, and only took a couple of minutes.

We implemented this solution using our in-house team.

This solution is a free of charge addition to our SQL licence. However, the only way this tool can be utilized is as a feature of the SQL licence, which may make it unattractive to organizations who don't wish to purchase the wider-ranging licence.

We highly recommend this solution as it is comparable with all of the major ETL software on the market. However, it should be noted that this is an enterprise class tool; it requires a team to be commissioned to do the proper development, there is a lot of standard documentation that comes with it, and a permanent team will be required to maintain it. So whilst it is a high-performing product, it requires a lot of commitment to optimize its use and capabilities.

I would rate this solution a nine out of ten.

We are using SSIS for applications in development and in production. We have applications that need to have a database to support them and those applications need to have different integration with other applications.

The most valuable feature of SSIS is its ease of use. It is easier to use than other applications.

The performance of SSIS could improve when comparing it to Oracle Database.

I have been using SSIS for a long time.

SSIS is stable.

This solution is good for small-scale developments. We have approximately 80 people using the solution.

I have used the support from SSIS and I am satisfied.

I would recommend this solution to others.

I rate SSIS a seven out of ten.

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.

The solution is primarily used for the ETL process. Another use case is transforming data from one format to another format.

The solution is easy to use and developer friendly. Many customizations can be performed with a good grasp of the C# language.

There are a lot of connectors that are not available right now. Some third-party connectors and adapters are available, but not directly from Microsoft data, which is an issue. And in terms of maturity, it is a good product. But, again, the way the industry uses these ETL tools, SSIS is not preferred because of many factors. Microsoft is no longer promoting the tool itself and is more focused on its cloud framework. That could be one of the reasons, but a smaller company prefers to SSIS because it is usually free with the SQL Server.

There are a lot of things that Microsoft could improve in relation to SSIS. One major problem we faced was when attempting to move some Excel files to our SQL Server. The Excel provider has a limitation that prevents importing more than 255 columns from a particular Excel file to the database. This restriction posed a significant issue for us, and as a workaround, we had to convert the files to CSV format before importing them. While it involved some manual effort, it was not a big deal since it was a one-time task. These are some small areas of improvement. There's one tool, a very famous and popular tool among banking clients, that supports this kind of data load in SSIS. 

Moreover, in the case of a pivot, which is available in your Excel, there are a lot of ways an Excel file can be created, and you can have a favorite kind of data format in Excel. Importing data of that kind into SSIS can be problematic, and it cannot be done easily. It requires writing some sort of custom code. These basic issues need improvements. 

However, I don't think Microsoft would be willing to make any modifications to the existing capabilities provided by the tool. The reason is that there are already many third-party vendors offering similar functionality through their plugins. 

For example, you can install these plugins within your Visual Studio, and they provide an extra set of features integrated into Visual Studio and SSIS. Perhaps that's why Microsoft has stopped actively improving upon certain features. But, again, this introduces an overhead in terms of development cost. To access additional tools or features, I have to purchase them from another vendor and then implement them. 

Moreover, if something is not directly supported by Microsoft and relies on third-party tools, it can become a significant issue, as I'll have to depend on those vendors, which poses another challenge.

I have been using SSIS for more than 12 years.

The solution is pretty mature.

I rate the solution’s stability a nine out of ten.

We have never faced any significant issues as long as your underlying hardware has a good amount of resources.

Scalability depends on the kind of workload and implementation you are giving to SSIS.

It is best suited for small and medium. However, for enterprises, it depends on the specific implementation they require. Real-time scenarios might not be the best fit, but for batch processing, it can still be suitable.

I rate the solution’s scalability an eight out of ten. It essentially gives most of the small and medium use cases, you will be easily able to implement and scale SSIS.

It is very difficult to get support from Microsoft. They will support you till they're getting paid. Microsoft is not interested in support in case of a small issue or help. It is very difficult to get support directly from Microsoft.

When it comes to ease of use, SSIS has an advantage over a tool called Informatica, which is also an ETL tool I've worked with. SSIS is more developer-friendly, even though Informatica provides GUI support. However, SSIS has a wider range of connectors compared to Informatica, making it easier to perform various transformations within the server itself. 

On the other hand, Informatica's repository feature is quite robust. SSIS has a repository feature but doesn't have its own implementation. To use a repository feature like DFS, Azure DevOps, or SVN, you need to purchase extra licenses and integrate them into your solution.

The initial setup was pretty simple. To install the SQL Server, select the feature during installation on the same server. In the case of a separate server, opt for SSIS service installation instead of installing the SQL Server, and it will be pretty quick. You can have your server up and running within ten minutes.

The solution is economical. It comes free with the SQL Server. You don't have to worry about the pricing as long as you're installing both services on the same server.

Overall, I rate the solution an eight out of ten. There is room for improvement.

SSIS' most valuable feature is its reporting services.

SSIS sometimes hangs, and there are some problems with servers going down after they've been patched.

I've been using SSIS for over eight years.

SSIS' stability is fairly good, but there's room for improvement.

The initial setup was pretty simple.

SSIS is fairly well-priced - I would rate it at four out of five.

SSIS is best suited for small and medium companies. I would rate SSIS eight out of ten.