SAP Business Warehouse, or SAP BW (formerly SAP NetWeaver Business Warehouse) is SAP's legacy data warehouse solution, now superseded by SAP BW/4HANA, and the SAP Data Warehouse Cloud which was launched in 2019.
SAP BW versions up to 7.4 have reached end of maintenance. SAP BW 7.5 support is extended to align with SAP Business Suite with NetWeaver components. For existing customers maintenance is scheduled to continue through 2027, with extended support available through 2030.
N/A
SSIS
Score 8.0 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Pricing
SAP Business Warehouse
SQL Server Integration Services
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
SAP BW
SSIS
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
SAP Business Warehouse
SQL Server Integration Services
Features
SAP Business Warehouse
SQL Server Integration Services
Access Control and Security
Comparison of Access Control and Security features of Product A and Product B
SAP BW is best for: 1. Large enterprises 2. Enterprises with 3+ legacy systems with entrenched users (politically difficult to merge) 3. Enterprises with employees who can understand both the technical capabilities of SAP BW and the needs of the business users - ability to speak both languages, otherwise the program could be unwieldy and potentially underutilized (it's not particularly inexpensive) SAP BW is less appropriate for: 1. Small enterprises 2. Enterprises who have well established, same location, CRM and UFS - the integration of data analysis will be easier and less expensive with other solutions 3. HANA
Ideal if the company is already a Microsoft shop, so chances are that it is free with SQL Server. Also, good for moving data between on premise systems. Not ideal for moving data to the cloud. No functionality out of the box to work with REST APIs. Stable product but definitely not the future
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.
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
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.
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.
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
SAP Business Warehouse scores higher in data warehouse functionalities for integration to SAP ERP and other SAP solutions such as SAP CRM, SAP APO, and SAP SRM. Standard SAP data source extractors which are available in SAP ERP can be used immediately for full or delta replication into SAP Business Warehouse. System governance in SAP Business Warehouse is top-notch with change management support for migration between system landscape from the development system to production system.
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.
Positive - This tool report output is in Excel so it's a good tool if your users are familiar with Excel.
Positive: this tool has rich BI content so developing extractors for standard processes from SAP ECC can be done in minutes.
Negative: It lacks lot of features which are available in other newer tools today. For ex. - rich charts, rich filtering, exporting capabilities, user interface.
Negative: Its not a plug and play tool like Qlikview, Lumira, or Tableau. Even a single report development in this tool takes a lot of time compared to others.
