SSIS Reviews

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.

We have some business requirements, and we use this solution to create the machine tables, measures and APIs.

It is an easy solution but needs some improvement. The creation of the measure in the DAC's model could be improved.

We have been using this solution for two and a half years, and it is deployed on-premises.

We use this solution with Visual Studio. Sometimes we open certain files without making changes, and it saves the changes. In Visual Studio, while we're using TFS, it is easy to backtrack the changes, and we can undo them. However, those changes are pushed to another server if we are not alert and in a hurry.

It is scalable, and we haven't faced many issues. Sometimes, there are storage issues, but it is more of a DBA problem. We have a team in India and France and four people from the Eurofins team using this solution.

I have personally used the technical support and they are good.

The initial setup was easy, and we also used some YouTube videos for guidance. We use the latest version, and it is based on C Sharp.

I rate this solution an eight out of ten. Regarding advice, SSIS is good. However, everything is shifting to cloud, and in other organizations, everybody's moving to Azure which is much easier to use. We haven't worked with Azure, so I can't compare it to SSIS at this time.

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.

I was using the solution to implement some business logic. What we do with the data collected is, for example, use it with Excel and some other databases. We do write our own logic to input the data into the SQL server. We'll be taking inputs and putting them into our business logic.

It is a very helpful tool to integrate. We can have our logic ready by putting data from different data sources, and based on our business requirements, we can have the logic created with the help of the SSIS package.

It allows us to use our own logic. We can create our own packages where it can help us to define the business logic.

It is easy to set up. The deployment is also very quick.

It is stable and reliable. 

The product is scalable. 

There aren't any improvements that are required for SSIS at the moment.

We'd like better data lake architecture so we can move SSIS to the data lake if necessary. Involving a data lake or data engineering aspects would be useful. While it is there, we need more features included. 

I've been using the solution for almost six years. 

The solution is stable. The performance is good. There are no bugs or glitches. It doesn't crash or freeze.

This is a very scalable product. You can expand easily.

We have 200 people using the solution. They are developers. 

I've never used technical support in the past. I don't have details as to how helpful or responsive they are. 

The solution is very straightforward. It's not overly complex. 

The package deployment takes some time. It depends on the size of the data which is being pulled in. For the normal setup, it hardly takes much time. For the most part, it is very fast.

I'm not sure of the exact cost of the solution. 

I'm an end-user.

We are using the latest version of SQL Server 2019. Typically, I start on-prem and move to the cloud. 

It's a good tool for merging data from various data sources. We can have automated administrative functions and data-loading features. We can populate the data for the data warehouse and for data merges. This is one of the best analytic tools for a person or enterprise. We can recommend it for data analysis and data analytics purposes.

I'd rate the solution ten out of ten.

SSIS orchestrates data transformation in the environment, which includes Oracle and SQL Server databases.

The most valuable aspect of this solution is that it is simple to use and it offers a flexible custom script task.

Connectivity to databases other than Microsoft. This is the Achilles' heel.

Integration with other vendors' connectivity should be available as well as being able to read and write data to databases or data storage other than with Microsoft.

There is connectivity with other databases, however, this is the most significant issue that has to be addressed.

I have been using SSIS for five years, but I first used it in 2007.

SSIS is quite stable.

SSIS is moderately scalable.

The company is fairly substantial. They have approximately 400,000 people in the company, but I am not aware of how many are using this solution. It is quite a bit.

There are a lot of developers using it.

I am not aware if they plan to increase their usage, it is not within my decision.

In terms of my immediate surroundings, we intend to use cloud tools, Azure technologies, and Microsoft. First and foremost, Microsoft ADF. Azure Data Factory is the cloud's SSIS replacement.

For this particular product, we have not used technical support.

I started with SSIS but then switched to IBM Datastage.

That was where I worked, this was already in use at another organization. 

I recently moved jobs, and this is the platform of choice for ETL once again. Informatica data center was used in various other organizations. 

I was attending Informatica workshops. I wasn't Informatica actively, but I might in the future, perhaps soon.

The initial setup is straightforward.

It only took five minutes to deploy SSIS. 

For maintenance, we rely on our platform team.

We will probably need one person for maintenance. Let's say it's only one person. But I'm not speaking on behalf of the entire company; I'm speaking on behalf of a single team of perhaps 1,000 people.

We did not use a consultant or third-party vendor, everything was done in-house.

This is difficult since it is included in the SQL server license. 

Depending on the arrangement that a certain company has with Microsoft, it may supply the permanent license that is included in the SQL server license, or it may be a time-bound license if it is a partner license or other enterprise license. 

I am not sure what our relationship with Microsoft is like or what the program is, but I believe it's some sort of enterprise license.

In the past, I worked with permanent licenses.

I would recommend SSIS to others who would be interested in using it.

I would rate SSIS an eight out of ten.

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.