SSIS Reviews

It was used for a couple of purposes, for example, we used it in our data warehouse when we wanted to create a dashboard that would give us an idea about, for example, the data itself. We had a client that would ask about a couple of requirements, like the past data from the last month or last year for a particular region for a particular client, and so on. I was using SSIS to store data incrementally and show the data using SSIS. 

For example, if we have created a couple of tasks or schedules, we would create a couple of packages and schedule them overnight. Every night it could fetch the data incrementally from the data warehouse. Every week, there was a requirement from the client that I need to add particular data to be changed and shared over email weekly. That particular data could be fetched from the data warehouse, and it will be shared with the client every week. 

Many features are very good in SSIS. 

I can create a particular package, and I don't need to repeat it again and again. For example, I can create a package that will fetch all the data from the given data. If my client gives me some data, I can clean some data, perform some transformations, and then store the data in any place. That's quite helpful for me as well. I don't have to do it again and again manually. I just have to create a package, schedule it, and it could be run, and it could be stored in any target I have. It can run for me, again and again, without me having to re-make it manually again and again.

It is easy to set up the product.

There are a couple of areas that could be improved. For example, if I created a package and the package would work on specific data, it could work on the performance or speed of the action. If you are working on a very large amount of data, then creating this package and performing some transformations might take some time. Everything just needs to be faster.

I haven't used SSIS for the last year, so I'm not sure about its new releases as of now.

In terms of its performance, it could be better. That could be something that would be easy and welcomed as an upgrade.

I'd like to see more dashboarding to be able to see the data through a graph. It would be great if I could also share the visualization with my clients.

I did use it in my previous organization for almost one year.

It is quite a stable product. There are no bugs or glitches, and it doesn't crash or freeze. It is reliable. I'd rate it a three or four out of five in terms of stability.

There are six teams using the solution in our company. 

I've never had to reach out to technical support. 

I'm not using Palantir Gotham. I just read about Palantir Gotham, and I'm not using it.

One of my clients wants us to use SSIS, and frankly speaking, if given the opportunity, I would say yes to using SSIS.

With SSIS, it is not difficult at all to set up. Many sources are there through which you can learn how to set up your SSIS. The documentation is great. With the help of documentation, it was very easy for me to set up.

Deploying a package would also not take a lot of time. It depends on what kind of package it is, however, it is pretty fast.  

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

I was a user. 

If you want to perform some transformation or data warehouse and the product is used for data analysis purposes, it's a good option. You can perform some transformation, et cetera.

I'd rate the solution eight out of ten. It was very useful for day-to-day tasks.

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.

We have a consolidated data warehouse. We use an SSIS tool as a pipeline to fetch the data from multiple sources such as Excel, CSV, Oracle database, or APIs. Further, we put the data into the SSIS database. We are using the solution for ETL purposes.

Previously, it took a lot of work to connect with multiple data sources. But now, we can connect with them easily using an external connector in SSIS.

Sometimes, we have issues with SSIS connectors while extracting data from Excel sources. They should improve this particular area for excellent compatibility.

I have been working with the solution for the last ten years.

It is a very stable solution. We have been creating a solution in SSIS, deploying it into the server, and scheduling it using SQL Server jobs. All the jobs have been running easily and quickly for the last ten years.

It is a scalable solution. I have around 800-900 users of the solution in our organization.

As I have been using the solution for the last ten years, I directly highlighted some questions to Microsoft. It is very easy to reach out to them, and I always receive support from them.

We used Informatica as well. We switched to SSIS as it took a lot of work to set up a pipeline in Informatica. Also, SSIS is more straightforward for the end user. 

The solution's setup was straightforward. It takes a day or two to complete the process. If you are good at development, the deployment process becomes easy. You only need a few resources to deploy the solution. I am handling deployment and maintenance all alone.

The solution is available at a lesser price than that of Informatica. I assume SSIS's enterprise version of SQL Server is pretty costly, but I must be aware.

The solution is easy to maintain. SSIS is a handy tool but requires vast knowledge to build the pipeline using it. I advise others to go for SSIS if the user is versed in developing a pipeline. Otherwise, you can quickly build a pipeline using multiple user-friendly solutions.

I rate the solution as a 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. 

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.

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.

We use SSIS to copy production data to Reporting Repositories. We use it for data movement from and to SQL or flat files such as CSV or fixed data.  This is primarily to build and update a data lake and data warehouse. 

More custom use cases are to do DQ validation comparing source to destination, and to extract data from bat files and SSIS files in order to build a metadata repository for documenting and mapping all the ETL packages.  We use this to find the packages responsible for any particular table or file, or vice versa.  This system, along with statistics logging, also gives us summary reporting capability.

I like that SSIS lets us build programs top-down. Starting with the control section, then drilling into the details of the steps make more sense than what Informatica requires, where you have to build each block first, then use a different tool to build the control structure.

In production, SSIS does a very good job of distributing work to many threads. It is robust and does a good job of handling overload conditions. It is simple for basic jobs, yet able to do very complex tasks. When all else fails, code can be written to make your own custom task or even tool.

I believe SSIS is not given the credit it deserves. SSIS does what most other new vendors tout as great features. But it is a very mature and stable product, unlike those others. It is supported by a larger company than many of those other products.

The error messages are pretty clear and point you to the problem well.

I am disappointed that Azure Data Factory did not stay closer to SSIS.

Data Flows are the main component we use. These can range from a simple source to sink ETL, to many source to many sink dataflows.

For flexibility and to make reading the logs in case of errors, I prefer not to put multiple copy operations in the same dataflow, although that is possible.  I try to keep in mind how to make production operations as easy as possible in case of failures.  I want to give the night crew the best opportunity for success when an error does occur.

We have about one error per 400 processes. About 3/4 of these were transitory issues with issues like slow connections and temporary outages. By making the code rerunnable, we can auto-restart on any error, and that resolves 3/4 without human intervention. This leaves any failure after two retries the only issue that the night crew has to do Root Cause Analysis (RCA) on.

We purchase an add-on called task factory primarily to allow bulk delete, update, and upsert capability. I'd like to see this be part of the standard package.

I believe there are ways to build a model and set variables so that it can be a generic process.

In my next system, I would like to have a generic process that would handle all the logging and processing in a model that can be modified and enhanced as the need for a better process, or different statistics to be logged is discovered.  I'd want this in a way that the model can be changed and all the processes, with their unique parameters, could all be changed with the model upgraded.

I believe they should add some features that help to create the code using a model. This would allow for continuous improvement of the model uses and easy replication of all the different programs that use the model.

15 years

Very mature and stable, and already has great performance features.

It can be very scalable both by adding memory or cores, and by running the SSIS on a farm of servers.

I did not really need much.  SSIS has a lot of excellent help available for a web search.

Positive

Prior solutions used SQL triggers

We have more control over the ETL with SSIS.

Installation is quite easy.  There are some drivers and setting you may need to make, based on the sources or sinks you need.  I am hoping these are more embedded in the install process, as I have not set up a server since 2015.

In house.  

good

SSIS is part of SQL server, in itself a very solid product.

You can run SSIS on the same SQL server instance where your data warehouse is, using the compute power at night to update, and during the day for reporting and data analysis.

I did not evaluate other options.  SSIS was available, and it worked well.

I later changed jobs to another company that used SSIS, and worked to improve and grow their data warehouse solution.

After using SSIS, we have tried talend, informatica, and spark solutions.  I would go back to SSIS, even for a non Microsoft shop, if I were allowed to.