SSIS Reviews

I use the company's solution to build dashboards and back-end data integration with Microsoft SQL Server and Power BI.

The most valuable features of the solution stem from the convenience it offers, along with the ability to refresh data.

The product's stability needs improvement.

The high prices attached to the product can be an area of concern where improvements are required.

I have been using SSIS for two years.

The tool's stability is okay. Stability-wise, I rate the solution an eight out of ten.

There are three to four people in my company who use SSIS, and around twenty to thirty people are dashboard users.

My company has a database administrator, so we don't use the support provided by the solution in our company.

The efficiency of the deployment and management tools of SSIS is a bit technical, but it is alright since our company's technical support has hands-on experience with it, and they can deal with the deployment part in a very minimal amount of time.

The product's deployment phase is easy.

To deploy the product, I followed the solution's online tutorial and downloaded the tool to configure it.

If you don't want to pay a lot of money, you can go for SSIS, as its open-source version is available. When it comes to licensing, SSIS can be expensive.

I have managed a complex data transformation process in my company with the solution's transformation functions. Previously, I worked at my company with the data streaming destination in SSIS.

For integration purposes, my company uses SSIS connection managers. With SSIS, I can also get data locally installed in Power BI and design the dashboard.

I mostly rely on the dashboards provided by Power BI instead of SSIS.

I use SSIS for the data integration process. I don't use Power BI that much for the data integration process.

The data warehousing capabilities of SSIS are okay.

If you are not using any product that offers integration services in your company, then you can start using SSIS for your organization's applications.

The debugging and error handling capabilities improved our company's data integration task, as the tool helped me detect many issues.

The benefit of the product is that there are a lot of online tutorials available about the tool. Users will not face any hurdles when trying to search for information about the product online.

I rate the tool an eight out of ten.

We primarily use the solution for getting the data from the application database and to the OLAP system. We extract the data from OLAP system and build data warehouses. Basically, this solution is used to build OLAP.

This tool works well when users aren't working with large amounts of data. 

It is easy to set up the solution. 

SSIS is very, very, very slow. It hangs a lot of the time. There is a buffer issue and a memory issue.

You need to keep a lot of packages. There's a lot of maintenance. 

The design is not user-friendly. 

They need to include a lot of connectors, and their component should be much faster. The component, transformation component, like lookup datatype conversion, doesn't work well for large amounts of data.  

I've been using the solution for two and a half years. I've used it for a while. 

It is quite stable. It's safe and reliable. A lot of organizations are using it instead of Azure Cloud.

I'd rate the scalability four out of ten. The solution does not handle large amounts of data well. Azure Data Factory is much, much more scalable. 

We've also used Azure Data Factory, which is much faster than SSIS.

The initial setup is not difficult. However, when the volume increases, it slows down. It's a bit of an obsolete tech stack and is not very current.

You only need one person the setup and deploy the product. 

We handled the initial setup in-house. We did not need outside assistance when handling the setup. 

I'm not aware of the exact pricing. It's being handled by another team. 

We're using Visual Studio 2019 and SQL Server Integration Services 3.16.

I'd advise potential users to go and learn Azure and use that. Use Data Factory, not SSIS. 

I'd rate the solution six out of ten. 

SSIS (SQL Server Integration Services) is primarily an ETL tool. It's frequently used for data integration and transformation. In the past, we used it to integrate data into our systems. Microsoft is now focusing on Azure Data Factory for cloud solutions, but SSIS is still a viable on-premises option.

SSIS utilizes SQL Server Management Studio (SSMS) for management. I've used SSMS for many years and find it quite user-friendly, even for those new to SQL Server.

Being a Microsoft product, it integrates well with Visual Studio, a familiar development environment. It also has a graphical interface that displays the ETL process step-by-step. 

It's a familiar tool within the Microsoft ecosystem, which has its advantages. 

It lacked robust cloud integration and sometimes struggled with specific data types from sources.

Another area of improvement is performance. It has always been an issue. 

I used it for more than ten years.

It is a stable product. I would rate the stability an eight out of ten. 

I don't believe SSIS is a major development focus for Microsoft right now. Performance enhancements are always a concern.

Scalability mainly depends on the underlying SQL Server installation. A more powerful server can naturally handle larger data volumes. There might be performance bottlenecks specific to SSIS itself.

There are around two to three end users in my department. There might be more in the company. 

I usually resolve issues on my own.

The setup was easy. All Microsoft products are easy to set up. 

It comes with SQL Server. We didn't have a separate license for it.

It does its job. I'd probably rate it a six out of ten. Performance could be better.

SSIS is a good fit if you're heavily invested in on-premises Microsoft products. If you have a more diverse tech stack, better ETL tools might be available. Microsoft often limits how its products interact with others.

Mostly we are receiving files in either XML or Excel and then we collect them in databases. Sometimes it's CSV and sometimes it is also Excel. Mostly, it is XML.

We have many regulations that we must follow, and this solution helps us manage that. There are rules that we must follow, and we get files in a uniform structure, and we need to import them into databases. Doing it with SSIS saves us a lot of time.

The performance is better than doing it in some alternative ways. We don't have to worry about so much manual work. 

Mostly it was helping us with importing XML files by checking the access and then doing some look-ups and containers to implement loops and things like that mostly. That was quite helpful in terms of saving time. 

Technical support is helpful.

No big improvements are needed at this time. 

At one point, we did have to purchase an add-on.

Since we are not using it for a whole ETL, or for a data warehouse, maybe I'm missing something.

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

The performance is very good. It makes it easier to do things that you would have to do differently otherwise.

I'd rate the overall stability eight out of ten. We haven't had any stability issues in many years. 

The scalability is pretty good. I'd rate the ability to expand at a seven out of ten. 

There are only three of us using the solution at this time. 

We contacted technical support maybe once. I don't remember when it was, however, once, we had to look at some dump size, and we called Microsoft to help us with that. They did help us, however, it was a very long time ago and I don't remember too many details about the problem or experience. 

While we are using it quite a lot, my understanding is that the company will go with Talend and not SSIS for a data warehouse project. I don't have any influence on that.

That said, we are not going to do any conversion from SSIS to Talend on what exists in our existing project. The data warehouse will be a totally new project, and they will go with Talend.

We did not use any other solution previously.

The initial setup is very easy. I'd rate it an eight out of ten in terms of ease of implementation.

The deployment itself only took a couple of hours. 

The installation that comes with SQL just requires some tweaking with Visual Studio or something like that. We had some problems with maybe deploying the product from the local machine, however, in the end, we solved it.

We have three people handling the initial setup. All of us are DBAs.

We handled the initial setup ourselves, in-house.

There are occasionally add-ons for SSIS that may increase the price. 

In the past, we did not evaluate any other solutions. 

We are end-users. 

The SQL version that we are using is 2019. However, I'm not sure about the exact version of SSIS we're using. We installed it with the 2019 version.

I'd rate the solution eight out of ten. 

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.

The use case is related to all reporting and transactions. On an hourly basis, we will pull the data for a few reports. Most of the time, it is a real-time integration between the applications.

Overall, it's a good product. I haven't had any issues with the product.

They can improve the solution in general. That said, I'm using around 30% to 40% of the SQL server. We have a separate team for the database administration site, so they probably have more of an idea of what needs to be improved.

We've had issues in terms of the amount of data that is transferred when we are scheduling. There are a few restrictions that we faced. In terms of the number of records, the limit can be increased. Sometimes what happens is not enough records are getting pulled, so sometimes the data is getting lost. After that, when the next schedule is running next time, the data is coming to our warehouse for data analysis. We need them to increase the limit of the data transfer on the schedule.

The initial setup was a bit difficult. 

I've been using the solution for seven or eight years.

The first time I attempted to deploy the solution, it was a bit difficult. However, it gets easier with time. 

I'd rate the ease of setup 6.5 out of ten in terms of ease of implementation. 

I don't do much on the deployment side and, therefore, can't speak to how long it takes to actually deploy.

We have around eight people on the solution working on the deployment in total. Around 5 are database administrators and there are three developers. 

I'm not sure which version of the solution I'm using. 

Before starting with SSIS, a person needs to understand the concepts of SSIS. They need some time to get comfortable with the product before jumping in. When I first started, I wasn't aware of a lot of things. Therefore, at first, it was a bit difficult. However, it gets easier with time. 

I'd rate the solution eight out of ten. It's flexible and very effective in terms of PLS skill programming. You can get real-time data from SSIS.

We are using SSIS for all of our relational database management systems (RDBMS) data.

The solution could improve by having quicker release updates.

I have been using SSIS for approximately 

The solution is stable.

The solution is scalable. With virtualization enabled we are able to scale horizontally.

We have approximately 2,000 users using this solution in our company.

The technical support is very good.

We have previously used Oracle.

We have approximately 12 administrators and managers that do the implementation and maintenance of the solution.

We have an enterprise license for this solution.

I would recommend this solution to others.

I rate SSIS a nine 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.