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.4 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
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 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.
Support comes slow. This is not a limitation of the software itself but could be a symptom from the local office. Once we get support everything works along smoothly.
It is always important to review the instructions. This is not a system that does well initially with personalization without review of standard procedures. A log of time can be lost if the technicians and programmers working with the data are not following correct procedures.
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.
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.
Exporting of data and reports to Excel is very easy for the end user to interpret and manipulate.
Negatively, the speed at which BW retrieves data and reports is very slow and out of date.
Addition of daughter application HANA has helped this aging application stay afloat for a few more years. Overall it has been a great tool but it's showing its age very fast.
