SAP Data Services offers more connectivity options without external connectors that must be purchased separately. Currently it has become a very robust platform with nothing to envy of its competitors, demonstrating very good results in all implementations. It handles many …
SAP Data Services is a very good tool and overall its easier to use than SSIS, but SAP is at a much higher price point than Microsoft. Microsoft can be a good fit for businesses of any size, but SAP tends to be a better fit for larger businesses.
These are all great products and, honestly, can move data faster. They include more enterprise features and have some great qualities about each. However, they all cost a lot depending on the implementation you need. With SQL Server Integration Services, you do not have any …
It's definitely one of the leading ETL tools, and it's the best ETL tool to use with SAP integration. If you use SAP HANA, then you should think about Data Services as your primary ETL tool.
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.
SSIS has been a bit neglected by Microsoft and new features are slow in coming.
When importing data from flat files and Excel workbooks, changes in the data structure will cause the extracts to fail. Workarounds do exist but are not easily implemented. If your source data structure does not change or rarely changes, this negative is relatively insignificant.
While add-on third-party SSIS tools exist, there are only a small number of vendors actively supporting SSIS and license fees for production server use can be significant especially in highly-scaled environments.
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
SQL Server Integration Services is a relatively nice tool but is simply not the ETL for a global, large-scale organization. With developing requirements such as NoSQL data, cloud-based tools, and extraordinarily large databases, SSIS is no longer our tool of choice.
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.
As other SAP products, there is excellent support by SAP on this tool. You can access the SAP Help portal in order to give support either from the huge community or directly from SAP.
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.
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
You cannot afford to run your business on questionable data. With SAP® Data Services software, you can access, transform, and connect data to fuel your critical business processes. Together, these enterprise-class solutions enable data integration and data quality, providing the right level of insight across your business so you can make better decisions and operate more effectively.SAP Data Services was previously known as SAP BusinessObjects Data Services, SAP BusinessObjects Data Integrator, BusinessObjects Data Integrator.
I had nothing to do with the choice or install. I assume it was made because it's easy to integrate with our SQL Server environment and free. I'm not sure of any other enterprise level solution that would solve this problem, but I would likely have approached it with traditional scripting. Comparably free, but my own familiarity with trad scripts would be my final deciding factor. Perhaps with some further training on SSIS I would have a different answer.