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. 

Prior solutions used SQL triggers

We have more control over the ETL with SSIS.

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.

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

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.

While executing tasks and managing data flow, we occasionally encounter Oracle system integration, and in the past, we have used Antunica, though it seems Microsoft's support for it has dwindled in recent years. Despite some versioning challenges, our workflow design, execution, and deployment have been relatively smooth using SSIS.

I've used free solutions or ones that allow you to create your own. I've used free ones like KNIME, etc. The open-source solutions have similar features, but I haven't found one with the same ease of use.

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. 

We did not previously use another solution. 

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.

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.

I worked on PowerCenter.

We switched to Data Factory, which is the cloud version of SSIS and the primary reason for the switch.

We have previously used Oracle.

We previously used Oracle as an integration tool, but it's much more expensive than Microsoft.

We decided to use SSIS because most developers know SQL Server. If they need to hire data engineers, they can just use generic languages like SQL Portal. You don't need to know Talend or other data warehouses and database engines. They prefer SQL Server because that's the most common product.

I also used Oracle Data Integrator as an ETL tool but it all depends on your need and customer preference. SSIS is being easy to use and things can be developed very quickly so I prefer to use SSIS for most of my data related tasks.

We were using Hyperion Application Link. We switched because HAL was being sunset.

I've always used SSIS. We never considered any other solution. We might have used some tools that were developed in-house occasionally, but by and large, we always use SSIS.

For the most part, we started with this solution. 

Previously, we used the .NET framework, which we are still using as well.

In my previous company, I was leading a team who were working with Informatica. Here, they stick to Microsoft technologies and are unwilling to change.

Prior to this solution, before 2005, we used DTS. 

Prior to using SSIS I used Informatica. I switched because my organization is using SSIS.

Based on the client's requirements, we switched over to this solution.

We previously used an in-house solution based on Oracle APEX.

Many customers are switching from IBM Datastage to SSIS. Think its the ease of use and license costs.

This is the first tool of this sort that we've used in my company.