It ensures that the database is restored to the most recent committed state after a restart and that transactions are either completely executed or completely undone. The persistence layer offers interfaces for writing and reading data. It also contains SAP HANA‘s logger that manages the transaction lo. Log entries can be written implicitly by the persistence layer when data is written via the persistence interface or explicitly by using a log interface.
In some business cases, it is required to use the same attribute view more than once.
In such cases, one can derive an attribute view using the base view which acts as reference to the base attribute view. The derived attribute view will be opened in the read-only mode. The only editable field will be its description. The derived attribute view will act as a reference to its base attribute view.
We use Life cycle management perspective to Upgrade/Updates for HANA studio.
Advantages of Column based tables:
Advantages of Row-based tables:
SUSE Linux Enterprise Server.
Loading data: There are several options available to get data into HANA. SAP provides a real-time replication server called SLT Replication. With this server you can replicate data from a SAP system or non-SAP RDBMS systems into HANA. The data is copied in its native format and will then need to be de-normalized on HANA using information views (attribute views, analytic views and calculation views). According to the documentation, you can also leverage the Sybase Replication Server for log based replication. In addition, Data Services 4.0 can be used to move data into HANA and can update data at near real time if needed. Data Services 4.0 can also de-normalize the data given its abundance of data transforms and provide data quality and cleansing transforms that will help clean the data before it is loaded into HANA.
Access the data: There are several ways to access the data within HANA. The ideal way to access data is through SAP Business Objects 4.@There are multiple tools within the Business Objects 4.0 platform for accessing HANA data. You can utilize Web Intelligence, Crystal Reports, Explorer, “Analysis Edition for Microsoft Office”, Mobile and Dashboard (Xcelsius). In short, any tool in the platform that supports ODBC or a Universe can be utilized to access data within HANA. These options work for SAP BW (powered by HANA) or for HANA (Standalone). If you have SAP BW powered by HANA, you can utilize any of the traditional query tools. For those that like viewing raw data results, you can utilize HANA Studios to execute SQL statements and view the results.
The component present in Persistence layer in the HANA DB is Page management & Logger.
HANA provides both a 32-bit and 64-bit ODBC and JDBC drivers. SAP Business Objects 4.0, Data Services 4.0 and many other SAP based tools have built-in support for these drivers to help support all the features HANA has to offer.
Oracle Enterprise, IBM Informix.
Navigator, Where-used list, Job log, Properties.
SAP HANA Modeling at a glance:
SAP HANA Information Modeling which also known as SAP HANA Data Modeling is the heart of HANA application development. You can create modeling views on top of database tables and implement business logic to create a meaningful report.
Transaction Manager controls the data processing in the HANA DB.
One reason is the number of CPU cycles per second is increasing and the cost of processors is decreasing. For managing the data in memory, there is five-minute rule which is based on the suggestion that it costs more to wait for the data to be fetched from disk than it costs to keep data in memory so it depends on how often you fetch the data.
For example: there is a table and no matter how large it is and this table is touched by a query at least once every 55 minutes, it is less expensive (in hardware costs) to keep it in memory than to read it from memory and if it is frequently accessed it is less expensive to store it in memory.
Since any changes in the source system are tracked in dedicated logging tables, the replication status for each changed data record is transparent. An entry of logging table is deleted after a successful commit statement from HANA database and this procedure ensures the data consistency between a source system and HANA system.
Recovers log between last data save point & time of failure.
Data services 4.0.