SAP Data Intelligence vs. SQL Server Integration Services (SSIS) vs. WSO2 Enterprise Integrator

If you have an SAP products ecosystem in your IT landscape, it becomes a no-brainer to go ahead with an SAP Data Intelligence product for your data orchestration, data management, and advanced data analytics needs, such as data preparation for your AI/ML processes. It provides a seamless integration with other SAP products.

Incentivized

As I mentioned earlier SQL Server Integration Services is suitable if you want to manage data from different applications. It really helps in fetching the data and generating reports. Its automation make it very easy and time efficient. It works well with large database as well. But it doesn't work well with real time data, it will take some time to gather the real time data. I would not recommend using it in a real time/fast-paced environment.

Incentivized

The best-suited scenario is the service chain pattern or all patterns used in online mode. The less appropriate scenario is a batch service the duration time of the service is more than 10minutes because it is necessary to increase the HTTP timeout.

• It integrates well with our current ecosystem of SAP products, like HANA.
• It provides end-to-end machine learning operations, with tools for the complete model life cycle.
• It has a simple user interface for novice users, with complex tools also available for power users.
• It builds on SAP Data Hub, providing all the ETL functions of that tool with additional machine learning functionality.
• It can run in the cloud, no on-premise software management needed.
• Many programming languages are supported, it provides a sandbox environment for the user to develop in whichever style they prefer.
• SAP is very actively developing and improving it.

Incentivized

• Standard ETL use cases for daily loads
• Loading incoming data from Vendors which is placed on FTP and adding them to the SQL Warehouse
• Creating outgoing data files and writing them to Vendor FTPs
• Easy Active Directory integration for seamless connections to SQL Server
• CI/CD by hosting the code on visualstudio.com

Incentivized

• Service chain pattern
• Message transformation
• Call more than one backend service
• Call service with different protocoll as the client use
• Use file as input
• Use mail as input

• Data transfer speed tends to be slow when there is poor internet connection since SAP Data Intelligence don’t synchronize data while offline. However, this is not vendor fault, that’s why we have implemented robust wireless technology internet connection in our organization.

Incentivized

• Connection managers for online data sources can be tricky to configure.
• Performance tuning is an art form and trialing different data flow task options can be cumbersome. SSIS can do a better job of providing performance data including historical for monitoring.
• Mapping destination using OLE DB command is difficult as destination columns are unnamed.
• Excel or flat file connections are limited by version and type.

Incentivized

• View deploy artifact in date time order
• Easy way to map data
• Easy way to manage payload

Allow collaborations among various personas
with insights as ratings and comments on the
datasets Reuse knowledges on the datasets for new users Next-Gen Data Management and Artificial Intelligence

Incentivized

Some features should be revised or improved, some tools (using it with Visual Studio) of the toolbox should be less schematic and somewhat more flexible. Using for example, the CSV data import is still very old-fashioned and if the data format changes it requires a bit of manual labor to accept the new data structure

Incentivized

I think the troubleshooting process might be streamlined with improved error recording and tracing. A lot of information about issues and how to fix them is hidden away in the Kubernetes pods themselves. I'm not sure whether SAP Data Intelligence can fix this problem it may be connected to Kubernetes's design, in which case fixing it could need modifications inside Kubernetes itself.

Incentivized

SSIS is a great tool for most ETL needs. It has the 90% (or more) use cases covered and even in many of the use cases where it is not ideal SSIS can be extended via a .NET language to do the job well in a supportable way for almost any performance workload.

Incentivized

SQL Server Integration Services performance is dependent directly upon the resources provided to the system. In our environment, we allocated 6 nodes of 4 CPUs, 64GB each, running in parallel. Unfortunately, we had to ramp-up to such a robust environment to get the performance to where we needed it. Most of the reports are completed in a reasonable timeframe. However, in the case of slow running reports, it is often difficult if not impossible to cancel the report without killing the report instance or stopping the service.

Incentivized

Initially we struggle to get help from SAP but then dedicated Dev angel was assigned to us and that simplify the overall support scenario. There is still room of improvement in documentation around SAP Data intelligence. We struggle a lot to initially understand the feature and required help around performance improvement area,

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

One of the reasons to pick SAP Data Intelligence is the speed and security it provides, in addition to the excellent support it provides. It is also compatible with all popular databases, which is another reason to choose it.

Incentivized

I think SQL Server Integration Services is better suited for on-premises data movement and ADF is more suited for the cloud. Though ADF has more connectors, SQL Server Integration Services is more robust and has better functionality just because it has been around much longer

Incentivized

We can start with the community version and then when we moved into production we can buy the supported version. The supported and community version have the same code so we can do every test before deciding to buy the supported version.

• Automation of data management slashed tasks by over 60% in most departments for the first 8 months.
• Metadata catalogs have enabled us to categorize data from disjointed sources in one place.
• It runs multiple ML models which enhances flexibility when managing data.

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

• Reduce development time to the service integration
• We can use junior developer
• Clustered in easy way