SAP BW powered by SAP HANA
SAP BW powered by SAP HANA: SAP Netweaver BW Powered by HANA has been introduced to market on April 10, 2012. SAP NetWeaver Business Warehouse (BW) powered with SAP HANA database replaces both the previous database and SAP NetWeaver BWA. This offers improved query/ load performance and simplified modeling, administration and infrastructure.
SAP NetWeaver BW 7.3 on HANA features SAP HANA-optimized Data Store Objects, SAP HANA In-Memory platform, SAP HANA-optimized InfoCubes , In-Memory planning engine , Consumption of HANA artifacts created via HANA studio and BW staging from HANA. SAP HANA-optimized Data Store Objects: SAP HANA-optimized Data Store object is a standard Data Store object that is optimized for use with the SAP HANA database. In SAP HANA optimized datastore object delta calculations are completely integrated in HANA. The use of in-memory optimized data structures for faster access as No roundtrips to application server are needed . Speeding up data staging to DSOs by factor 5-10. There is also a tool to support Tool support for converting standard DSOs into SAP HANA-optimized DSOs.
SAP HANA-optimized InfoCubes: SAP HANA-optimized InfoCube is a standard InfoCube that is optimized for use with SAP HANA The standard InfoCubes tailored to a relational database consists of fact tables and dimension tables. SAP HANA optimized InfoCubes represent “flat” structures without Dimension tables and E * tables.
Improved Query performance: With HANA, the BW InfoCubes and DSO’s leverage column store and In-Memory Calculation Engine for query acceleration. Index for Infocubes and Infoobjects are no longer required.
BW In- Memory Planning: SAP HANA on BW replaces the traditional Planning process which runs the planning functions in the Application Server with In-memory Planning runs all planning functions in the SAP HANA platform .In Memory planning also offers a number of capabilities such as Aggregation, Disaggregation.
SAP NW BW on HANA:
|Service pack||Release date|
|SAP NW BW 7.30 on HANA||Released on 10 April 2012|
|SP8||Projected Q4 2012|
- HANA-optimized InfoCubes and Data Store Objects (DSO)
- Simplified and faster data modeling
- In-memory planning
- Performance boost for data loading, query response time and planning
- SAP BW and SAP HANA Mixed Scenarios
- “Not active” data concept
- Support of Semantic Partioned Objects (SPO)
- Enhanced Partitioning for write optimized DSOs
- BW/Non-BW mixed EDW environments
- Open Operational Data Store layer
- Big Data/Hadoop connector
- HANA optimized transformations
1.2 Obsolete functions and tools
SAP HANA database makes the SAP NetWeaver BWA obsolete. There is no need to create and fill indexes, using SAP NetWeaver BWA. Aggregates do not improve performance in SAP HANA environment. Building/deleting the index for InfoCubes are no longer required using SAP HANA and offers improved performance and Simplified administration and infrastructure.
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, as read accesses are in-memory optimized. In addition, the query performance on Data Store objects is comparable to the performance on InfoCubes. Load processes in SAP HANA-optimized Data Warehouse objects can be processed with a high degree of efficiency.
The SAP HANA database replaces both the previous database and SAP NetWeaver BWA, thus contributing to a reduction in infrastructure costs. Instead of database administration and additional SAP NetWeaver BWA administration, the SAP HANA database requires just one set of administration tools, for monitoring or backup and restore for example. Data modeling is simplified. Using in-memory optimized objects means that it is not necessary to load to a BWA index for example, while the database architecture allows you for example to delete characteristics from an InfoCube that still contains data. Loading data from a Data Store object into a downstream InfoCube can also become unnecessary, if the InfoCube is only there to improve query performance.
Thanks to its high compression rate, the column-based data store ensures that less data needs to be saved. Column-based storage is used for all Info Providers that save data. The property "SAP HANA-optimized" improves performance even further.