Database Reference
In-Depth Information
SAP product availability matrix
For a complete list of version requirements for SAP BW on HANA,
check the SAP product availability matrix (PAM) for each tool to en-
sure connectivity for existing data sources.
http://scn.sap.com/docs/
It can be difficult to quantify this speed improvement in terms of financial savings. Let's
look at a simple example.
Let's assume that there are 2,000 query executions per day and the average time is 20
seconds in the legacy database. The total time spent waiting for query results is over 11.1
hours per day. With SAP HANA, the wait time is 1.2 hours per day, which is a saving of
9.9 hours per day, or 2,376 hours per year!
Even data loads into traditional InfoCubes and DSOs are around twice as fast (at least) as
loading data into a traditional BW system. This means you can load data twice as many
times per day as you did before migrating to SAP HANA and still have more spare time in
your load window!
The database size for BW on HANA is significantly smaller than the size required in tra-
ditional BW and BWA systems. The speed of the in-memory SAP HANA calculation en-
gine allows super-fast aggregation of data and faster access to raw data, so there is no need
to pre-calculate aggregates or invest in obsolete hardware for the BW Accelerator (BWA).
SAP HANA is also a columnar database which allows for significant compression com-
pared to relational databases. Generally, a compression factor of 3-5 times is expected for
most tables compared to Oracle, for example. The speed of the SAP HANA database also
eliminates the need to build InfoCubes in SAP BW and hence, eliminates additional data.
This allows your company to spend less on licensing and lowers the total cost of owning
an SAP BW on HANA system.
