I spent some time compiling my own list of the benefits of running BW on HANA instead of the traditional a traditional RDBMS under BW for a customer. I thought it might also make a decent blog topic. There is no particular order in terms of importance etc.

Benefits of using the SAP HANA Database for BW

  • BW functions performed within SAP HANA benefit from its in-memory and calculation engines, accelerating BW data access.
  • Existing BW client tools, like SAP Business Explorer, are fully supported on BW powered by SAP HANA. Direct clients, like Microsoft Excel and SAP’s Business Objects Business Intelligence (BI) tools, are also supported by BW on HANA.
  • With BW in-memory-optimized objects, complex analysis and planning scenarios with unpredictable query types, high data volume, high query frequency, and complex calculations can be processed with a high degree of efficiency.
  • Loading SAP HANA-optimized BW objects can also be done more efficiently.
  • The SAP HANA database replaces both any previous database and SAP NetWeaver BWA, reducing infrastructure costs. Instead of both database administration tools and additional SAP NetWeaver BWA administration tools, the SAP HANA database requires just a single set of administration tools for monitoring, backup and restore, and other administrative tasks.
  • Data modeling is simplified. Using in-memory-optimized objects you do not need to load a BWA index, for example. In addition, the architecture of the HANA datbase allows you to delete characteristics from an InfoCube that still contains data.
  • With its high compression rate, the column-based HANA datastore requires less data be materialized.
  • BWA is not required anymore.
  • Aggregates are not required anymore. You no longer need processes for creating and filling aggregates.
  • You no longer need processes for creating and destroying Indexes on Infocubes.
  • Obsolete Process Types: The following BW process types are not needed if you use the SAP HANA database to support BW:
    • Initial Filling of New Aggregates
    • Update Explorer Properties of BW Objects
    • Rolling Up Filled Aggregates/BWA Indexes
    • Adjust Time-Dependent Aggregates
    • Construct Database Statistics
    • Build Index
    • Delete Index
  • Note: If you are using the SAP HANA database, it is no longer possible to select these process types in process chain maintenance. Existing process chains do not have to be modified. The relevant process variants do not run any tasks in the chains and do not terminate with errors.
  • SAP HANA-optimized objects help you to achieve significantly better performance in load and activation processes. Up to 80% faster for loading in HANA Optimized Cubes.
  • Uses a Delta Merge for new data. Delta storage is optimized for write access. Main storage is optimized for read access.

Benefits of BW Analytic Engine on HANA

  • Calculation Scenarios: The system automatically generates, updates and deletes the logical indexes associated with InfoProviders.
  • There is no need to create and fill indexes.
  • No need for aggregates.
  • The system creates logical indexes for the following InfoProviders:
    • Standard InfoCube
    • SAP HANA-optimized InfoCube
    • InfoObjects as InfoProviders
    • Analytic Index
    • CompositeProvider
  • With Calculation Scenarios, complex calculations for various OLAP functions are performed directly in the database. These functions include:
    • Hierarchies
    • Top N and Bottom N Queries
    • MultiProviders
    • Selected exception aggregation including required currency translation.
  • BW workspaces: A BW workspace is a special area, where new models can be created based on central data from  the BW system and local data. Workspaces can be managed and controlled by a central IT department and used by local special departments. This means  you can quickly adjust to new and changing requirements. The aim of workspaces is to bridge the gap between the central requirements and the flexibility required locally. Central architected data marts from the IT department can be combined, in a workspace, with data marts from the specialized departments.
  • Analytic Indexes and Transient Providers: You can create a TransientProvider by publishing SAP HANA models in the BW system. The SAP HANA models published in the BW system are saved as an analytic index. This represents a view of the data in the SAP HANA model. A TransientProvider is generated on this analytic index. A TransientProvider based on an SAP HANA model is suitable for ad hoc data or scenarios that change frequently. If the SAP HANA model is changed, the analytic index is adjusted automatically at runtime. HANA Models are published to analytic indexes in transaction RSDD_HM_PUBLISH. Analytic views and calculation views are available as SAP HANA models.
  • Composite Provider: These TransientProviders can then be linked to other BW InfoProviders in a CompositeProvider. This enables you to combine ad-hoc data with consolidated data from the BW system and also use the OLAP functions of the BW system for analysis. If the SAP HANA model is changed, the analytic index is adjusted automatically at runtime. Analytic views and calculation views are available as SAP HANA models.
  • VirtualProvider: You can create a VirtualProvider based on a SAP HANA model if you want to use this model in the BW system. Analytic views and calculation views are available as SAP HANA models. Unlike the TransientProvider based on a SAP HANA model, the VirtualProvider based on a SAP HANA model is suitable for stable, long-term scenarios. This VirtualProvider can be used in a MultiProvider. In addition, navigation attributes can be used. To use navigation attributes, you can select InfoObjects with master data access Standard or SAP HANA Attribute View.
To report this post you need to login first.

9 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply