A. Changes in Tenant Database Management.

Fallback Snapshots for Tenant Databases (New)

You can create a fallback snapshot for a tenant database. It allows you to revert to a particular database state. A fallback snapshot may be useful if you perform changes to the contents of a database that you may need to roll back quickly, e.g. if you upgrade to a new version of an application.


Reinitialisation of an Unrecoverable System Database (New)

You can reinitialize the system database with information on all tenant databases of the SAP HANA instance using the command-line toolhdbmdcutil. This may be necessary if the persistency of the system database has been damaged and cannot be recovered.


Port Number Change of Tenant (New)

You can change the port number of a tenant database by executing the ALTER DATABASE statement.


B. Persistent Data Storage (New and Changed)


1. Persistent Memory (New)

Persistent memory (non-volatile RAM, also referred to as Storage Class Memory) is supported in SAP HANA as a persistent storage type. The persistent storage functions as DRAM memory and is used specifically for main data fragments of the column store. Delta data continues to be stored in DRAM. Usage of this feature can be configured so that it can be applied independently at four levels: database, table, partition, column.


2. Partitioning Data Volumes (New)

Data volumes on the indexserver can be partitioned so that read and write operations can run in parallel with increased data throughput. The indexserver data volume can be partitioned so that data can be segmented and distributed over several stripes on the disk to improve performance.