A short overview of the SAP HANA Performance Management Tools in SAP HANA 2.0 SPS00

SAP HANA capture and replay

Testing application workload can be a huge effort for users, developers and consultants alike. Also, things do not get easier on a large scale, especially for moving from one revision or SPS of SAP HANA to another.

Initially released with SAP HANA1 SPS12, SAP HANA capture and replay offers semi-automated support for integrated testing in the context of SAP HANA., the goal being to simplify the manual effort needed for creating tests and performing a more accurate replays than what is possible with other approaches.

Move HANA data and log files to different mount point

I decided to write this because I ran into a space problem while trying to upgrade a HANA test system. Of course, it isn’t a certified appliance, but I had to move the data and log files to another mount point to free up enough space to complete the upgrade.

Moving data files to a different mount point is a common procedure for many databases, but typically isn’t an issue with HANA’s appliance model. HANA has a very specific hardware configuration with the persistent mount point being 4 times RAM. The introduction of the Tailored Datacenter Integration (TDI) may warrant this process a little more often. I’ve outlined the steps below to move the $(DIR_GLOBAL)/hdb/data and $(DIR_GLOBAL)/hdb/log directories to a different location.

How to view Historical Data in SAP DB Control Center

The Historical Data feature in SAP DB Control Center (DCC) collects and stores system health status information. This feature, however, is not automatically enabled. This document will guide you through setting up data capture and different options for data visualization.

Note: This document was originally created by a former colleague of mine, Yuki Ji, in support of a customer engagement initiative regarding the SAP DB Control Center (DCC) product.  To preserve this knowledge, the document was migrated to this space.

The information in this document applies to DCC SP10 or higher.

The purge period of historical data collection needs to be configured according to the capacity of the system hosting DCC and the number of systems being monitored. Relation between systems monitored and space needed can be found in the DCC documentation. Otherwise to enable historical data and configure purging requires only two SQL statements to be run.