Oracle Data Integrator (ODI) vs. SQL Server Integration Services (SSIS)

I tried various ETL tools and here is [where and] why I recommend Oracle Data Integrator. 1. When you want to process structured data from different databases - Teradata, Exadata, DB2, SQL, Oracle etc. 2. Oracle Data Integrator supports all platforms, hardware, and OS. This is a major advantage compared to other leading tools. 3. The ELT architecture giving a cutting edge performance over leading ETL tools. There is no need to align Oracle Data Integrator between source and target. ODI uses the source and target servers to perform complex transformations. 4. Speeds up the development and maintenance by reducing the code that developers need to write

Incentivized

Ideal for daily standard ETL use cases whether the data is sourced from / transferred to the native connectors (like SQL Server) or FTP. Best if the company uses MS suite of tools. There are better options in the market for chaining tasks where you want a custom flow of executions depending on the outcome of each process or if you want advanced functionality like API connections, etc.

Incentivized

• Converts data from various sources into one target format using various business logic rules and integrates with various DBMS types.
• Transformed data from DB2, SQL Server and other Oracle databases into flat files and then used ETL jobs to load into Oracle DB target
• Data Integrator and Goldengate were used together to accomplish the data movement needed for business and data consolidation in live environment. Data Integrator helped with development and in reducing lead time to convert data into target.

Incentivized

• SSIS works very well pulling well-defined data into SQL Server from a wide variety of data sources.
• It comes free with the SQL Server so it is hard not to consider using it providing you have a team who is trained and experienced using SSIS.
• When SSIS doesn't have exactly what you need you can use C# or VBA to extend its functionality.

Incentivized

• Oracle support is not the best when needing help with the system
• The documentation is also very poor and takes very long to generate
• Some parts of it are not intuitive to use and get hard to troubleshoot
• Like other Oracle products, you must have very, very thorough knowledge about their systems to understand
• Like all Oracle products, cost is high

Incentivized

• SSIS memory usage can be quite high particularly when SSI and SQL server are on the same machine
• SSIS is not available on any environment other than Microsoft Windows
• SSIS does not function with any database engine back-end other than Microsoft SQL Server

Incentivized

It is maturing and over time will have a good pool of resources. Each new version has addressed the issues of the previous ones. Its getting better and bigger.

SSIS is responsible for running core business processed managing core business data. It can be managed, improved and expanded using minimal internal resources. It is also able to support all of our current data infrastructure. Replacing SSIS would be time consuming and costly with no apparent ROI.

Incentivized

It is easy to learn, works great on many features, but needs improvement on ETL troubleshooting and performance monitoring functionality. Great tool on Microsoft stack. it is great with simple, structured datasets. Once logic gets fancy like nested conditionals
complex joins,
reusable transformations, versioned logic …SQL Server Integration Services (SSIS) packages become hard to read and harder to maintain. Source control is painful. Errors can be cryptic
Logging takes effort to set up well
Debugging in production is limited.

Incentivized

Raw performance is great. At times, depending on the machine you are using for development, the IDE can have issues. Deploying projects is very easy and the tool set they give you to monitor jobs out of the box is decent. If you do very much with it you will have to write into your projects performance tracking though.

Incentivized

The support, when necessary, is excellent. But beyond that, it is very rarely necessary because the user community is so large, vibrant and knowledgable, a simple Google query or forum question can answer almost everything you want to know. You can also get prewritten script tasks with a variety of functionality that saves a lot of time.

Incentivized

The implementation may be different in each case, it is important to properly analyze all the existing infrastructure to understand the kind of work needed, the type of software used and the compatibility between these, the features that you want to exploit, to understand what is possible and which ones require integration with third-party tools

Incentivized

Talend Data Integrator has been evaluated during the setup of the architecture for a customer, in comparison to ODI, since it's an open source ETL. But, differently from the meaning of "open source", it has licence costs too that aren't that different from ODI ones. Moreover, the other components of the business intelligence architecture of the customer were Oracle, so we thought that ODI would suit at best with them, more than a different vendor software.

Incentivized

Both are very similar. Azure is cloud based. It is easier for the organization who uses cloud based application. The SQL Server Integration Services is cost effective. Azure was more on the expensive side for our organization. Azure was a little complex, it needed special training to use it. Azure was not accurate with complex data.

Incentivized

• Oracle Data Integrator helps provide a business with the data it needs to defend the decisions it makes.
• Oracle Data Integrator allows you to analyze data from what can be separate, different, and often outdated data sources. It allows you to make direct comparisons when analyzing data from different pieces of equipment.
• Data from Oracle Data Integrator was used to analyze manufacturing quality and drive down spoilage, saving the company money.

Incentivized

• Without this, we would have to manually update a spreadsheet of our SQL Server inventory
• We would also have poor alerting; if an instance was down we wouldn't know until it was reported by a user
• We only have one other person who uses SQL Server Integration Services , he's the expert. It would fall to me without him and I would not enjoy being responsible for it.

Incentivized