Tenant Database Management
Fallback Snapshots for Tenant Databases
Fallback snapshot can be created for a tenant database, which allows you to revert to a particular database state. This feature is more useful incase if you want to perform any changes to the contents of a database that you may need to roll back quickly like incase if you are planning to upgrade to a new version of an application.

Port Number Change of Tenant
By executing ALTER DATABASE statement you can change the port number of a tenant database.
ALTER DATABASE Statement (Tenant Database Management)

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

Persistent Data Storage

Persistent Memory
The non-volatile RAM which is also referred to as Storage class Memory is supported as a persistent storage type in SAP HANA .This memory is also called as persistent memory. This feature can be configured can be applied independently at four levels: database, table, partition, and column. The persistent storage carries out the functions as DRAM memory and is used specifically for main data fragments of the column store.

Partitioning Data Volumes
This is one of the feature which improves the performance by distributing the segmented data over several stripes on the disk. Data Volumes on the indexserver are partitioned in such a way that read and write operations can run parallel with increased data throughput.

Table Maintenance
Default Table Type
The default table type has been changed in SAP HANA 2.0 SPS 03 to column-type tables. A configuration parameter is available to override this behavior if necessary.

Heterogeneous Partitioning
This feature helps in giving more flexibility in partitioning second-level partition schema to tables with different second-level range specifications for each first level partition. It also helps in tracing sub partitions on hosts, hosts which support extended storage for dynamic tiering.

System-Versioned Tables
System-versioned tables in SAP HANA SPS 03 will eventually replace the existing history tables feature. They support the tracking of changes on column store tables. This is done by capturing the validity period of each record.

Table Redistribution
This new configuration option in Table redistribution has been introduced to provide a series of weighting parameters to influence the priorities of the redistribution.

New configuration options have been introduced to table redistribution to provide a series. When executed from the command line using the CALL REORG_GENERATE () command you can include configuration parameter values with the call which apply only for the current session. In this way you can test redistribution options by repeatedly generating, reviewing, and optimizing the plan before it is finally executed.

Workload Management and Engines
Configuration Parameter Tracking
Parameter tracking is now available to improve traceability of configuration changes. This feature maintains a history of changes to configuration values including details of the time the change was made, the user name, the current and previous values. Optionally, a reason for each change can be entered in a comment value.

Workload Management
In the area of workload management new configuration parameters are available for admission control so that timeout values can be set for queued jobs, and workload classes also now support a statement timeout value which can either be set in a workload class or as a configuration parameter.

SQL Plan Stability
SQL Plan Stability is a feature to protect the performance of queries by capturing query plans in a source system and reusing them in a target system to regenerate the original query plan. The Plan Stability feature could be used, for example, when upgrading from SAP HANA 1.0 to SAP HANA 2.0 (the feature is also available for capture purposes in SAP HANA 1.0 SPS 12).

Processing Engines for Improved Statement Performance
New processing engines offering better performance when executing SQL queries continue to be developed and are being phased in to SAP HANA: the SAP HANA Execution Engine (HEX) and the Extended SQL Executor (ESX). Configuration parameters are available to disable these engines if necessary; hints for queries are also available to either avoid or prefer the use of these engines.

SAP HANA HDBSQL Options
The new -strictSeparatorLine option removes the parsing of a single quote, double quote, and BEGIN…END nesting. Separator line matching is strict and no leading or trailing spaces are allowed. When -c is not used, the default separator is a semi-colon on its own line.
• The new /read interactive option reads commands from the specified batch file.
• The new -printoutput option specifies how output from the SQLScript print library is handled.

Statement Performance Analysis

Client-Side Data Encryption
With client-side data encryption, columns that contain sensitive data, such as credit card numbers or social security numbers, are encrypted by using an encryption key accessible only by the client. Column data is encrypted and decrypted on the client.
To use client-side encryption, your interface must meet a number of requirements. These are documented in the SAP HANA Client Interface Programming Reference.

Numerous new privileges and SQL statements have been added to support client-side encryption. For more information, see support for client-side encryption in the section SAP HANA SQL and System Views Reference.

Client-Side Data Encryption

Client-Side Data Encryption

Configuring the Client for Client-Side Encryption and LDAP

SAP HANA SQL and System Views Reference