SAP HANA CAPTURE AND REPLAY What is capture and replay? Current features & product benefits.
It enables in real simulation of workload without the need of other 3rd party tools
It Provides competitive replay and does analysis for SAP HANA database
Helps in ensuring that the landscape changes will not effect or do not degrade system performance and its efficiency
Minimizes or Reduces manual effort for testing the changes in customer deployments
When should Capture and replay to be Used? When to need to improve the focus on stability and improve the focus on performance of your production servers SAP HANA Workload Analyzer.
What is workload analyzer? Current features & product benefits
In this tool the Web-based UI is integrated into SAP HANA cockpit
Provides flexible, chart-based analysis options and gives further insight into system and the workload
Provides Solution for analyzing database performances
The Database performance is analyzed using thread samples and engine instrumentation
Gives a sophisticated approach and Provides timeline analysis
It also helps in filtering capabilities
It Allows administrators to view the current state and health of a system at a glance
In case of bottlenecks, it supports multi-dimensional performance analysis to evaluate them
Helps to Drill-down or to evaluate possible root cause of performance issues which is carried out either by analyzing real-time, historical or captured data
SAP HANA SQL Analyzer
What is SQL ANALYZER?
Features In HANA SQL Analyzer the Web-based UI integrated into SAP HANA cockpit Helps to analyze different aspects of executed SQL query
Provides start point for each and every query-level performance analysis
Has similar functional scope as PlanViz view present in the SAP HANA Studio
Provides deeper insights into SQL-based queries and SQL Script-based queries
Designed to be dedicated web-based application
Works in collaboration with other Performance Management Tools
Complements full end-to-end view of system performance
SAP HANA Workload Management
What is workload in the context of SAP HANA?
It is a set of requests with common characteristics, e.g.
request source (user, application, etc.)
Types of query (analytical, transactional, etc.)
Hierarchy of Business (high, low, etc.)
System Level Objectives (SLOs) (response time, throughput, etc.)
Workload has certain resource demands to the system
Mixed workloads compete for shared system resources…
If a request consumes a significant amount of system resources, other
Requests are subject to queuing effect
Waiting workloads might fail to meet their expected performance
Options for managing workload Settings on operating system level
CPU-binding is a resource pooling technique on OS-level and outside the view of the SAP HANA database. We recommend to use SAP HANA parameter settings first
Partitioning CPU resources on process-level
–within single SAP HANA instance
–between SAP HANA instances
–between SAP HANA tenants
Binding CPU resources to processes
–Guaranteed CPU resources on process-level
–Ensures data locality per CPU-socket
–Keeps specific resources dedicated to specific applications or use cases
Options for managing workload Settings on SAP HANA system level SAP HANA global settings can be done as parameter changes in the database .ini files. These parameters affect the complete SAP HANA system.
SAP HANA supports NUMA-aware data placement, hash-distributing tables and partitions across NUMA nodes; this ensures faster processing between memory and CPU. SAP HANA also supports NUMA-aware job scheduling, taking into account the NUMA location of tables when scheduling jobs.
CPU –thread pool size for complex, long-running statements (e.g. OLAP) and SAP HANA system tasks and for short-running requests (e.g. OLTP)
Degree of Parallelism –statement thread limit for the SAP HANA system
Memory –global allocation memory limit for the SAP HANA system
–statement memory limit for the SAP HANA system
Options for managing workload Settings on SAP HANA session level SAP HANA workload classes allow the dynamic mapping of SAP HANA resources to SAP HANA DB clients based on workloads. Workload classes define resource properties on statement level granularity
Create workload classes defining:
statement thread limit
statement memory limit
Define mapping rules based on session variables
APPLICATION USER NAME
Options for managing workload Limit resources per application, user or workload class
Option to limit CPU/memory prior to SAP HANA 2.0 SPS02:
Options on system/global level:
–Statement thread limit
–Statement memory limit
Options on session level: –Workload classes can be used to assign resource properties to incoming connections
–Resource limitations offer statement thread limit, statement memory limit, statement priority
–Mapping is done via sessions variables (APPLICATION NAME, USER NAME, CLIENT, etc.)
Only work on statement level; multiple statements from one application, user or workload class can not exceed their limits, but parallel statements cannot be limited
Options for managing workload Settings on SAP HANA session level – session variables
This is used to pass the SAP HANA session variables with their client-specific values to SAP HANA incase SAP HANA client-application wants to get benefitted by SAP HANA workload classes
SAP HANA 2.0 SPS00: setting of SAP HANA session variables for use with workload classes is improved
In order to ensure that workload classes can be mapped and used correctly, there are several options for JDBC/SQLDBC connections to set session variables implicitly
First option: In the first phase we need to get meaningful default values from OS. This is possible and ensures that some variables are always passed and set.
Second option: Optional passing of variables through connection string. These variables overwrite the variable values coming from the first option.
This can be set in the connection string by the user, but not by the developer or partner or vendor.
Third option: Explicit setting of session variables via setClientInfo()
This can only be done during the development phase.
If the partner/vendor chooses to call the setClientInfo() function, this overwrites any values coming from the first and the second option.
Dynamic Admission Control
Used to handle short peak-load situations
Correctly sized hardware
We can avoid or remedy the contention issues by rejecting incoming request
Helps in tracking of recent CPU and memory consumption
Handles the requests only at Session Layer
Request via HTTP to XSC, TrexNet, and other internal calls are not considered
Affects newly-invoked statements,and doesn’t show any impact on running statements
By default it is disabled, and can be configured via ini-parameters in indexserver.ini
Secure Code: SAP Netweaver AS Add on for code vulnerability analysis
SAP Enterprise threat detection
Manage users & Permissions
SAP Identity management
SAP Access Control
Secure helps in preventing unauthorised access to your business system which is crucial for the organisation security. They offer secure, convenient single log in for all business whether its on premise and in cloud.
With ever increasing cyber crimes SAP Threat Detection allows you to maintain your system Landscape in Real time
Benefits of Single Sign on On premise and in cloud
We can secure and authenticate our Applications and landscape with one strong password, optionally with additional factors
This helps in Eliminating the need for password reminders on the post-it notes
We can secure all passwords and keep them protected, in one central place
Efficiency gains as users now have to remember only one password
Higher productivity can be reached due to the reduced efforts involved in manual authentication, password reset, etc.
There will be Low TCO of running a secure landscape by management of server-side certificates
It’s a Lean product which can be implemented faster phase in implementation project, quick ROI
There will be no more need to provision, protect, and reset the passwords among many systems
There will not be any requirement for password policies across many systems
SAP Single Sign-On for on – premise landscapes
Simple and secure access
Provides Single sign-on for SAP desktop clients ,web applications and for mobile devices
SAP provides Support for cloud and on-premise landscapes as well
Secure data communication
Data Encryption is provided for communication with SAP GUI and other desktop clients
It provides Digital signatures options
FIPS 140-2 certification of cryptographic functions
Advanced security capabilities
It involves in Two-factor and risk-based authentication
Authentication can be done with smart cards or RFID tokens
There will be Simplified lifecycle management of the server-side certificates
SAP Cloud Platform Identity Authentication service
The access protection option provides Identity federation and web single sign-on which is based on SAML 2.0
It Secures the landscape integration with on-premise authentication servers
Though its Social-, two-factor- its risk-based authentication
Manage users and access to applications
It helps in User administration and integration of user stores with on-premise
Extends User groups and application access management
It is basically User self-services
Has Password and privacy policies to be followed
Enterprise features for integration
Helps in Branding of end user UIs
offers Programmatic integration via SCIM* standard
SAP Single Sign On Main Scenarios & Capabilities
In this scenario if you Authenticate once to an authentication server (MS-Active Directory, AS ABAP,..)
The security token required confirms your identity to login to business applications. This is done for each and every subsequent login done to the business application
With this option you can Authenticate each time you when you access a business application
Authentication is done against a central authentication server and not the business application itself
In this type of authentication additionally to the information about password, you need to authentic and carry a physical element (example mobile phone, RSA SecurID card, etc.)
There is an option to Implement both single sign-on and multiple sign-on
Programmatic integration is done through SCIM* standard
Focus on simplicity
Simplicity is key for SAP Single Sign-On.
The Security capabilities should be easy to implement and use them. We should not make the Customers feel or carry the weight of the implementation efforts against the benefits of running a secure landscape. So make it simple with single sign -on.
Simple software roll-out
As part of the regular SAP Kernel the cryptographic library is shipped and updated regularly
The desktop client is installed using SAPSetup and can be easily integrated into the SAP GUI roll-out
There is no need to install add-ons, or any need to modify the ABAP sources
Simple configuration You can use standard ABAP transactions SPNEGO and SNCWIZARD for the configuration
There is no need to work on the server command line
SAP Single Sign-On is tightly integrated into the SAP NetWeaver stack, re-using its existing, proven infrastructure and security framework
The digitization of the workforce and advent of Cloud technologies has caused an enormous shift in the enterprise technology market. The market needs today is enterprise-class adoption of the Internet of Things (IoT), artificial intelligence, next-generation analytics, and much better integrated business applications. Market leaders like SAP and Oracle invested heavily to move from on-premise to the cloud.
SAP adopted a strategy of combining key acquisitions and building innovative solutions that meet the market demand. They acquired leading cloud-based solutions like Ariba, Concur, and Success factors. Starting with HANA they have delivered S/4 HANA and a suite of BI solutions to the market that meets various business needs.
The purpose of SAP HANA was to simplify SAP solutions and deliver a more agile and productive solution. It was a solution to the business need for real-time processing of transactions and analytics for all of a company’s data. The advent of modern microchip technology resulted in explosive processing speeds and brought in-memory processing of data mainstream. SAP HANA is a relational database management system that combines OLAP and OLTP processing into a single in-memory database. It eliminates the use of aggregated data and indexes which experts found caused 60% to 90% of application complexity. SAP HANA provides the foundation over which new generation of applications and solutions are built. It delivers an enterprise system that is fundamentally simpler, with high productivity, agility and performance.
S/4HANA, the Next generation Intelligent ERP for Digital World .Designed based on three words Immediate, Intelligent, and Integrated. S/4HANA is a suite of solutions that runs on top of HANA. It can be run on SAP’s managed private cloud platform or in the public cloud with AWS, Azure or Google Cloud, or a customer’s own on-premise data centre. In 2015 SAP’s CEO Bill McDermott as “our biggest launch in 23 years, if not in the entire history of the company”. S/4HANA delivers all core ERP capabilities in one place, with one underlying data store. Currently the major modules being implemented are Simple Finance and Simple Logistics. SAP claims adoption by more than 6000 clients globally.
SAP has a great suite of Business Intelligence products that are available as on premise or in the cloud solutions. These products give actionable information that leads to effective business decisions. SAP continues with its time-tested Web Intelligence and Crystal Reports products while improving on its Data Visualisation and Analysis tools. Xcelsius has been taken out of the roadmap and Lumira 2.0 combines Lumira and design studio for data visualization needs. SAP RoamBi caters to the mobile-centric analytics and data visualisation needs. The latest offering SAP Analytics Cloud aims to offer access to all data so that business users can easily discover, visualize, plan and predict. This solution is fully cloud based. The buffet of BI tools available enables a potential client to choose an offering that meets their exact business need.
SAP is having very good success in the market with their new products. In their fourth quarter financial statement in SAP has raised its targets for 2020, predicting that “strong momentum” in cloud services would pave the way for more predictable and higher revenue streams.
With the growing demand of SAP HANA market, In order to keep up with the change, the people in the SAP industry will have to upgrade their skills. Comprehending the need for this transition Ripples Info Under the expert guidance with a vision to produce Subject matter experts for the industry demand with a simplified learning process.
SAP HANA Platform 2.0 SPS 03 introduces new and changed features for the administration of SAP HANA.
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
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.
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.
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 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.
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.
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