SAP BW/4HANA is a next-generation
data warehouse solution. It is specifically designed to use the advanced
in-memory capabilities of the SAP HANA platform. For example, SAP BW/HANA can
integrate many different data sources to provide a single, logical view of all
the data. This could include data contained in SAP and non-SAP applications
running on-premise or in the cloud, and data lakes, such as those contained in
the Apache Hadoop open-source software framework. With SAP BW/4HANA,…
SAP BW/4HANA is certainly an excellent choice when it comes to setting up a data warehousing platform within a landscape of existing SAP systems ecosystem for realizing quick time to value and ROI over the long term. Many non-SAP analytics tools such as Power BI , Qlik also now offer connectors to leverage SAP BW/4HANA data as additional options to deploy third party visualization tools which make it a more open ended platform of choice. But with the future roadmap of SAP and industry in general being focused towards cloud based offerings (SAC and Datasphere) infused with AI capabilities one has to make a judicious choice among these depending on the use case, capabilities of platforms and existing systems landscape and the overall long term IT strategy. SAP BW/4HANA may not be a good platform of choice if starting a native greenfield data warehousing implementation with cloud first approach which would require data integration across SAP and Non-SAP sources and one should consider other SAP cloud offerings which however still have some time to reach a level of maturity as SAP BW/4HANA has reached over the years.
Microsoft SQL is ubiquitous, while MySQL runs under the hood all over the place. Microsoft SQL is the platform taught in colleges and certification courses and is the one most likely to be used by businesses because it is backed by Microsoft. Its interface is friendly (well, as pleasant as SQL can be) and has been used by so many for so long that resources are freely available if you encounter any issues.
With ODP based extraction, SAP BW/4HANA does well to integrate the data from various source systems like S4HANA , S4C.
With composite providers having the ability to integrate HANA calculation views, we are able to make the best of use of both application layer and data base layer(HANA) for mixed modelling scenarios.
with data tiering optimization higher data volume are effectively handled as we have the option to control the amount of data that is being stored in HOT , Warm and cold storage. With data volume grows over the year, DTO comes in handy solution to automatically move the delta to appropriate area based on temporature.
It would be nice to see tools available within SAP BW/4HANA for cross platform esp. other SAP systems integration from a data extraction and scheduling standpoint. This is to ensure BW data stays consistent with its sources and is refreshed only after completion of core business process activities in its source systems. This is also relevant from a SAC and Datasphere integration standpoint for data being fed from SAP BW/4HANA as these platforms currently only support time based scheduling options with no dependencies possible against SAP BW/4HANA processes. Currently most companies employ an external third party scheduling tool to manage this.
With the advent of Analysis for Office the ability to publish AFO workbooks has been lost directly from the SAP BW/4HANA platform unlike its BEx Analyzer predecessor which had the Broadcaster. The use of BO Platform is not an ideal use case for this functionality which is very basic in its scope.
In this age of AI would be nice to see functionality introduced for AI co-pilots like Joule to speed by data modeling and scheduling activities as well as a natural language based querying options within AFO.
Microsoft SQL Server Enterprise edition has a high cost but is the only edition which supports SQL Always On Availability Groups. It would be nice to include this feature in the Standard version.
Licensing of Microsoft SQL Server is a quite complex matter, it would be good to simplify licensing in the future. For example, per core vs per user CAL licensing, as well as complex licensing scenarios in the Cloud and on Edge locations.
It would be good to include native tools for converting Oracle, DB2, Postgresql and MySQL/MariaDB databases (schema and data) for import into Microsoft SQL Server.
We understand that the Microsoft SQL Server will continue to advance, offering the same robust and reliable platform while adding new features that enable us, as a software center, to create a superior product. That provides excellent performance while reducing the hardware requirements and the total cost of ownership of our solution.
SAP BW/4HANA requires specialized skillsets around data warehouse modeling and the access to data, however the modeling capabilities are intuitive and have now become accessible to both SAP and non-SAP data warehouse specialists. This new model allows for Interchangeable skillsets and access to a broader pool of experts throughout the industry, as well as easier access to data.
SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.
SAP Max Attention and general support for SAP BW/4HANA is broadly available. Truth to be told, MaxAttention has a premium cost but brings great engineers. So this being an enterprise capability and extremely critical, we did not consider cost as the main factor since support works well. Just keep that in mind when making your selection.
We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.
Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.
SAP BW / 4HANA and SAP IQ are both used for warehouse; with quick consultations for business analysis and that allows us to obtain dashboards and KPIs efficiently. SAP IQ is columnar and SAP BW / 4HANA immemorial. SAP BW / 4HANA was selected for the response speed of the queries since it saves the information in cache.
[Microsoft] SQL Server has a much better community and professional support and is overall just a more reliable system with Microsoft behind it. I've used MySQL in the past and SQL Server has just become more comfortable for me and is my go to RDBMS.
with SAP BW/4HANA's ability to store historical data and provide trends data for analysis, it supports business to make strategic decisions based on not only current data but also with historical data from several years in the past. It has helped to improve the accuracy
with automated process chains for data loading and automated support to fix common errors, with support for automated data cleansing, the operational cost has reduced a lot for the business
BW being the Single source of truth for the reporting eliminates the ambiguity in reporting by different business area.
Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.
