In traditional data warehouses, such as SAP BW, a lot of pre-aggregation is done for quick results. That is the administrator (IT department) decides which information might be needed for analysis and prepares the result for the end users. This results in fast performance but the end user does not have flexibility.
The performance reduces dramatically if the user wants to do analysis on some data that is not already pre-aggregated. With SAP HANA and its speedy engine, no pre-aggregation is required. The user can perform any kind of operations in their reports and does not have to wait hours to get the data ready for analysis.
This is a transfer routine (ABAP) defined at the info object level; this is common for all source systems.
Yes, either globally or using query debug tool RSRT.
A structure consisting of InfoObjects without persistence for connecting two transformations.
These cubes are used for both read and write; standard cubes are optimized for reading. The transactional cubes are used in SEM.
Display only and navigational; display only attributes are only for display and no analysis can be done; navigational attributes behave like regular characteristics; for example, assume that we have a customer characteristics with country as a navigational attribute; you can analyze the data using customer and country.
DIM ID: are used to connect fact tables and dimension tables.
This is to distribute data per time; for example, if the source contains calendar week and the target contains calendar day, the data is spit for each calendar day. you can select either the normal calendar or the factory calendar.
Row based tables:
Column based tables:
Any system that is sending data to BW like R/3, lat file, oracle database or external systems.
No; the cube must be empty to do this; one work around is to make a copy of the cube A to cube B; export data from A to B using export data source; empty cube A; create partition on A; re-import data from B; delete cube B.
The SAP HANA database is developed in C++.