An analysis should ideally be carried out before a HANA project (database migration, S / 4HANA product switch). However, it is possible at any time.

In any case, an analysis should be carried out in good time before the upcoming SAP system measurement. Since a possible early notification to SAP gives you additional room for negotiation and usually secures the regularly granted discount, this opportunity should be used early in order to create clarity.

We work with you to forecast upcoming projects. This gives you an indicator for possible budgeting rounds in the context of license and hardware costs.

Even with a good archiving strategy, the data in the system will grow steadily. With new projects, a lot of unplanned data is often created. HANA features such as NSE can already be used to optimize memory usage with the existing system resources.

NSE is a HANA feature that was delivered with HANA 2.0 SPS04. No further license is required and is already included in the standard. The name stands for Native Storage Extension. A further buffer layer (warm data) is added to the existing HANA storage architecture (hot data). The data is displaced from the memory to the hard disk using an LRU (Least Recently Used) principle. This means that a multiple of the warm area can be stored.

The existing system architecture is retained. Nothing needs to be adjusted for system copies or HANA system replication. The data remains part of the HANA. You only have to define which data is to be outsourced.

For the end user, this often ends in a barely noticeable impairment in performance (3-5%), which is accepted when selecting old data.

There are 2 starting points for using NSE which are dependent on the workload of the database:

• less knowledge of business processes and their interaction with the DB load: Analysis via NSE Advisor
• Existing knowledge: selective use of NSE based on the load

In the case of a complete analysis with all components (technical as well as commercial / legal), a framework and the expected goals are defined at the beginning.

In the sizing workshop, the system (s) is examined and a forecast is made based on the last few weeks. Possible memory leaks are also identified here and suggestions for optimization are made.

In the next step, the currently used DB functionalities are checked and listed.

This data is then mapped using the License Ethics tooling.

In the final step, the license workshop, all results from the previous points are processed.

• Are the features really necessary?
• Are there still existing contracts that cover these purposes?
•  Are you under - or over licensed?
•  Are there any other technical ways to save something?

Yes, if you have already collected the necessary data yourself or want something specific to be analyzed, only special steps of an analysis can be carried out. This is then tailored to your needs.