Professional Documents
Culture Documents
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 01
Course Duration:
SAP Copyrights, Trademarks and
Disclaimers
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see https://www.sap.com/corporate/en/legal/copyright.html for additional
trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical errors or
inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any
reason without notice. The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking statements are subject to
various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.
Demonstration
Procedure
Warning or Caution
Hint
Facilitated Discussion
TARGET AUDIENCE
This course is intended for the following audiences:
● Technology Consultant
● Database Administrator
● System Administrator
Lesson 1
Introducing the SAP HANA Cloud 3
Lesson 2
Introducing the technology behind SAP HANA Cloud 9
UNIT OBJECTIVES
● Introduce SAP HANA Cloud as a part of the SAP Business Technology Platform
● Identify the technical background of SAP HANA Cloud
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Introduce SAP HANA Cloud as a part of the SAP Business Technology Platform
Animation
For more information on this topic please view the animation in the lesson
Introducing the SAP HANA Cloud in your online course.
On-prem landscapes are often large and complex best-of-breed system landscapes. This
means customized solutions for dedicated business areas. All these purpose build solutions
can't work standalone, they need to interact with each other to support the company’s
business processes. These system landscapes often consist of hardware, operating systems,
databases and business applications of different vendors, so maintaining them takes a lot of
effort from the IT department.
Large data volumes with different formats is inherent to the best-of-breed approach. This
situation arises on its own due to the use of business applications from different suppliers.
These applications have all their own data formats and data stores. This makes it difficult to
exchanging data with applications from other vendors.
Siloed data in different locations is again inherent to the best-of-breed approach. Most
business applications store their data in a database, but every business applications vendor
has its preferred database type. This means that important master and transactional data like
is stored in different databases and servers. It takes a lot of effort from the IT department to
keep all this data up-to-date and in-sync over all the different locations.
Complex Infrastructures is also inherent to the best-of-breed approach because different
applications support different databases, operating systems and hardware. All these systems
need to be able to interact with each other because the business application need to be able
to exchange data between each other. This makes the infrastructure complex.
Data compliance is very important in today’s world. Companies have to setup procedures to
ensure that sensitive data is managed and organized in such a way that business rules and
legal and governmental regulations are met. Breaking these rules could lead to reputation
damage (bad press) and financial damage (fines for breaking the rules).
When making the move to the cloud, all the above points have to be taking into account as
well! It's not like “storing your data in a cloud” auto-magically make the above pain points go
away. A thorough investigation in the capabilities and features of the cloud provider need to
be conducted to ensure that all business requirements are met.
The SAP Intelligent Enterprise vision helps companies to become an intelligent enterprises,
enabling companies to make impactful changes to run their business better by growing more
resilient, more profitable, and more sustainable.
In simple terms an Intelligent Enterprise, is a company that is using modern cloud-based
technologies, like Artificial Intelligence (AI) and the Internet of Things (IoT), to better use its
data to get real-time insights about its operations, market environment and customers. The
journey to become an Intelligent Enterprise is not something that can only be started by the
Fortune 500 companies, it’s also the SMB’s who see the opportunity to transform their
business models to become more customer-focused, more innovative, more flexible and
more responsive to market demand.
At the core of the Intelligent enterprise the SAP Business Technology Platform (BTP) brings
business data, including Operation data (the O) that explains the what and Experience data
(the X) that explains the why, to the business processes.
See the following video for an overview about SAP Business Technology Platform Capabilities.
The SAP BTP provides ONE unified and connected platform for all data-driven innovations to
turn DATA to into VALUE. This is orchestrated by the solutions Database & Data
Management, Analytics, Application Development & Integration Services and Intelligent
Technologies.
The SAP Business Technology Platform is built to fit into deployment scenarios that are best
aligned with your company’s growth strategy, whether it’s cloud, on-premise, hybrid or multi-
cloud strategy.
With the SAP BTP, you can make confident decisions and re-imagine business processes that
provide Exceptional Experiences to your customers, employees and partners to succeed in
the Experience Economy.
The journey to the cloud to become an Intelligent Enterprise isn't something that far away on
the horizon, it's happening right now. Research shows that by 2022 almost 75% of all
databases will be deployed or migrated to a cloud platform1
Reasons for moving to the cloud are:
● Data explosion in volume size
● The countless number of different data types and data sources
● Flexibility and timely delivery of hardware and software resources
● Lower TCO
1 Gartner Research, G00347472, The Future of the DBMS Market is Cloud, June 2019
SAP HANA Cloud is a fully managed in-memory multi-tier cloud database as a service
(DBaaS). As the cloud-based data foundation for SAP Business Technology Platform, SAP
HANA Cloud integrates data from across the enterprise, enabling faster decisions based on
live data.
Animation
For more information on this topic please view the animation in the lesson
Introducing the SAP HANA Cloud in your online course.
SAP HANA Cloud combines several important features in one product. The following features
are part of SAP HANA Cloud:
● Multi-Service Database
Combining the known SAP HANA qualities like in-memory, multi-model, hybrid
transaction, and analytics processing in real-time with high volume and extreme
transactionally focused services.
● Data On Demand
All data, regardless of size, category, and complexity, available to you whenever you need
it.
● Easy Integration
A unified access layer to simplify data processing while consolidating and harmonizing
data integration to your intelligent applications.
● Power Of The Cloud
Cloud qualities like low TCO, elasticity, serverless principles, high availability, resilience,
and autonomous behavior.
● Streamlined Access
Simplified data-access which connects all your information without demanding that all
data be loaded into a single storage solution.
● Developer Experience
SAP HANA Cloud provides a integrated development environment in which the developer
can develop and model custom applications.
Summary
In this lesson you have learned how SAP Intelligent Enterprise vision in build on top of the SAP
Business Technology Platform that provides all the required technology in one platform.
SAP HANA Cloud is one of the four pillars of the SAP Business Technology Platform and
provides the database and data management services to handle constantly growing data
volumes in central place.
LESSON SUMMARY
You should now be able to:
● Introduce SAP HANA Cloud as a part of the SAP Business Technology Platform
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Identify the technical background of SAP HANA Cloud
The SAP HANA Cloud, SAP HANA Database is a cloud-native platform that reduces the
complexity of multi-cloud or hybrid system landscapes. SAP HANA Cloud provides all of the
known advanced SAP HANA on-prem technologies for multi-model data processing in-
memory or on disk with the benefits of the cloud.
Comparing SAP HANA Cloud with SAP HANA on-prem show that many administrative tasks
are handled as a managed service by the cloud provider. In SAP HANA Cloud the following
administrative tasks are handled by the cloud provider:
● Selection, purchase and provisioning of servers and storage.
● Installing, configuring and upgrading the operating system.
● Installing, configuring and patching the database software.
● Backing up and restoring and recovering the database software.
● Tuning the database to run optimal on the underlying operating system and hardware.
As a database administrator you are still in control and you can deploy new SAP HANA
database instances with the required RAM, CPU and disk resources whenever you need them.
The big advantage is you don't need to go through the whole hardware buying, configuring
and software installation process.
The automated processes within SAP HANA Cloud make sure the SAP HANA database with
the requested hardware resources is available within minutes instead of weeks or sometimes
months.
Database patching is fully automated and is basically reduced to a stop and a start of the SAP
HANA database. The moment in time when the database patch is applied is fully controlled by
the database administrator.
The SAP multi-cloud foundation build around of the following three environments:
● Cloud Foundry environment
The Cloud Foundry environment allows you to create polyglot cloud applications in Cloud
Foundry and is based on the Cloud Foundry Open Source Cloud Application Platform.
Cloud Foundry is an open source, industry standard Platform-as-a-Service (PaaS)
technology for developing and deploying cloud applications in both private and public
cloud environments. It’s designed to run on a variety of Infrastructure-as-a-Service (IaaS)
providers, such as Amazon Web Services, Google Cloud Platform, Alibaba Cloud, and
Microsoft Azure. It uses a container-based architecture that executes applications in any
programming language and lets you choose from different runtimes and backing services.
SAP is a platinum-level founding member of the Cloud Foundry Foundation, which
oversees the development of Cloud Foundry software and its ecosystem. To provide an
open and portable platform to run and manage web-based applications and services in a
cloud environment, it has adopted the open source Cloud Foundry technology as basis for
its SAP BTP Cloud Foundry environment. You can use it to enhance SAP products and
integrate business applications, as well as to develop entirely new enterprise applications
based on business APIs.
For more information, see the Cloud Foundry project website: https://
www.cloudfoundry.org/
● Kyma environment
The Kyma environment is a runtime you can use to build cloud-native Kubernetes-based
extensions.
It's a fully managed Kubernetes runtime based on the open source project "Kyma", which
lets you extend SAP solutions with serverless functions and combine them with
containerized microservices. It ensures the smooth consumption of both SAP and non-
SAP applications by running workloads in a highly scalable environment and building
event-based and API-based extensions.
Every Kyma environment consists of:
- A Kubernetes cluster provisioned on a cloud provider and region (data center) of your
choice.
- The open-source project Kyma installed in its latest version on the provisioned cluster.
The SAP HANA Cloud is build on top of SAP's Multi-Cloud foundation in the cloud Foundry
environment and running a inside Kubernetes as a container.
Animation
For more information on this topic please view the animation in the lesson
Introducing the technology behind SAP HANA Cloud in your online course.
What is a Container
Containers are very similar to Virtual Machines (VMs), but there are significant differences.
For example, containers share the host operating system and run on top a container runtime,
whereas VMs run on top of a hypervisor and have their own guest operating system .
Therefore, containers are considered more lightweight then VMs.
What is Kubernetes
Kubernetes is a cluster management system for container orchestration that allows you to
manage and control your containerized applications. The name Kubernetes originates from
Greek and means "Helmsman" or "Pilot".
Kubernetes is based on Google's Borg cluster management system and was open sourced by
Google in 2014 as Kubernetes. In the Kubernetes world you will often see the term Kubernetes
abbreviated to K8s.
For more information, visit the Kubernetes website: https://kubernetes.io/
The SAP HANA Cloud provides the database and data management service to SAP Analytics
Cloud, SAP Data Warehouse Cloud, SAP Business Applications and third party applications.
Animation
For more information on this topic please view the animation in the lesson
Introducing the technology behind SAP HANA Cloud in your online course.
Within SAP HANA Cloud you have the choice between several storage options. The storage
options are:
● SAP HANA Cloud, SAP HANA database
SAP HANA Cloud allows real-time data virtualization for federated on-prem and cloud data
sources.
The SAP HANA Cloud lets you consume the SAP HANA database data from applications
running on SAP Business Technology Platform, as well as from applications running on-
premise or in other cloud services using the standard SAP HANA clients. The SAP HANA
Cloud provides simplified data access to connect all your information without the need to
have all data loaded into a single storage solution.
Developers and modelers can use the SAP HANA transformation and modeling features on
SAP HANA Cloud database instanced as well as on on-prem databases. SAP HANA Cloud is
capable of handling structured, semi-structured or unstructured (remote) data sources.
SAP HANA Cloud also provides the possibility to create hybrid landscape by using the SAP
HANA Smart Data Access (SDA) and SAP HANA Smart Data Integration (SDI) capabilities.
A common replication SQL Interface is available that combines SDA Remote Table
Replication and standard SDI based Replication. Optimized for SAP HANA to SAP HANA
Cloud replication with Remote Table Replication, a native SAP HANA feature, using the
transaction layer logs.
Flexible connectivity options are available via standard SDI replication supporting any data
source. In-memory or Native Storage Extensions (NSE) are available as storage options
storage options for the table replicas in HANA Cloud.
Remote Table Replication is supported between on-premise SAP HANA SPS05+ and SAP
HANA Cloud via the SAP Cloud Connector.
Summary
In this lesson, you have learned about the underlying technology of SAP HANA Cloud. You
now know which services the cloud provider manages. You also have now a basic
understanding of the technologies used in the SAP Business Technology Platform.
LESSON SUMMARY
You should now be able to:
● Identify the technical background of SAP HANA Cloud
Learning Assessment
X A Intelligent Technologies
X B SAP NetWeaver
2. In which non-SAP public clouds can you deploy SAP HANA Cloud?
Choose the correct answers.
X A Alibaba
X B IBM
X C Salesforce
X D Google
Lesson 1
Creating your personal SAP.com account 18
Exercise 1: Create SAP.com account 21
Lesson 2
Creating your personal SAP BTP trial instance 24
Exercise 2: Create a SAP BTP Trial Instance 27
Lesson 3
Connecting using the SAP BTP Cockpit 31
Lesson 4
Connecting using the Cloud Foundry CLI 35
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create your personal SAP.com account.
Business Case
Your company wants to make the move to the cloud and perform the digital transformation
that is required by this decision. In your role, as a database administrator, you need to have a
clear insight in the SAP HANA Cloud capabilities and features to be able to integrate these in
to your companies digital transformation vision.
To get a better insight in the capabilities of SAP HANA Cloud, you want to create a SAP.com
to be able to explore the SAP HANA Cloud functionality in your SAP Business Technology
Platform trial instance.
SAP HANA Cloud is available as a free trial, but you need a SAP.com account before you can
log-on to the SAP BTP to explore the SAP HANA Cloud features. Creating a SAP.com account
only takes a few minutes. You can start the sign up process by following these steps:
3. On the Registration page, fill out all the required fields, provide a strong password and
specify contact preferences. Confirm that you read the SAP.com Terms and Conditions
and click the Register button to complete the registration.
As a last step in the registration procedure, you need to go to the e-mail account you
specified. There you will find a verification e-mail from SAP. Open that e-mail and press the
Click here to activate your account button to finish the verification process and
activate your SAP.com account.
As soon as your SAP.com account is successfully activated, you will be forwarded to your
SAP.com dashboard. You can use the SAP.com dashboard to change your account setting
(e.g., set your profile to private (default) or public, add a profile picture, or write a BLOG post).
Changing your account settings is optional, the account you have created is fully operational.
Log-on to SAP.com
Before you can use the SAP Business Technology Platform (BTP) to explore the SAP HANA
Cloud features you need to log-on to the SAP BTP using your personal SAP.com account.
Note:
If you don't create a sap.com account in advance, then the account will be
automatically created as soon as you create a free SAP HANA Cloud trial.
Summary
In this lesson, you have learned how to sign up, activate and log-on to a free SAP.com
account. You will use this SAP.com account to create your free SAP Business Technology
Platform (BTP) instance. In the SAP BTP instance you then can explore the SAP HANA Cloud,
SAP HANA database features. You have also learned the procedure to use a SAP BTP trial
instance via your enterprise SAP BTP account.
LESSON SUMMARY
You should now be able to:
● Create your personal SAP.com account.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create your personal SAP BTP trial instance.
Because you are already logged on to SAP.com with your personal SAP.com account the
process will start immediately. The Welcome to your free trial pop-up tells you where in the
SAP BTP you can find SAP HANA Cloud. Click the Click here to start your trial!
button to start the creation of your SAP BTP trial instance.
If this is your first log-on to the SAP Business Technology Platform trial account, you will get
redirected to the SAP ID Service for a telephone number verification. Follow the following
steps to activate your SAP ID:
1. In the Verify Your Telephone Number window, fill-in your mobile telephone number. With in
a few minutes, you will receive a verification code on the specified telephone number.
Enter the received code in the Code input-field.
Note:
If for some reason the code isn't received, you can request to send a new code
by pressing the Request New button.
2. Press the Continue button to complete the telephone number verification process.
3. Read the SAP BTP Terms and Conditions and mark the check-box.
4. Press the Accept button to complete the SAP BTP trial legal disclaimer process.
The SAP Business Technology Platform trial setup process takes only a few minutes, but you
have to perform the following steps to complete the process.
1. In the Welcome to Your Personal Trial window, select the region that is closest to you. Your
instance will be setup in a data center in that region to make sure the network latency is
minimal.
3. The SAP Business Technology Platform trial setup process takes only a few minutes. The
progress is shown in the Welcome to Your Personal Trial window.
Summary
In this lesson, you have learned how to create your free SAP HANA Cloud trial instance on top
of the SAP BTP trial.
LESSON SUMMARY
You should now be able to:
● Create your personal SAP BTP trial instance.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Log-in using the SAP BTP Cockpit
You are redirected to the SAP Business Technology Platform Trial landing page, press the Go
To Your Trial Account button to open your SAP BTP trial account.
After you have registered yourself, use SAP HANA Cloud Trial as a direct link to the SAP
HANA Cloud trial account.
Note:
On the SAP Business Technology Platform Trial landing page you will find many
tutorials on how to navigate and use the SAP Business Technology Platform
The SAP HANA Cloud trial instance has a one year lifespan. An inactive account will be
suspended after 30 days of inactivity. After these 365 days the SAP HANA Cloud and all the
content you have created will be deleted.
Hint:
Make sure that you have saved all your content before the SAP HANA Cloud
instance is deleted after 365 days
If you want to use a SAP HANA Cloud trial in your enterprise SAP Business Technology
Platform account, then you first need to log on to the enterprise SAP BTP using your business
e-mail address. The procedure is explained in the following steps:
Note:
Select the Remember me check-box to allow the SAP ID Service to set a cookie
and you will be logged on automatically for the next three months.
3. When Two-Factor Authentication is activated for your account, you will have to open the
SAP Authenticator app and get the generated passcode. You need to enter the time
limited passcode before you can log on to your enterprise SAP Business Technology
Platform account.
Figure 22: Use SAP HANA Cloud Trial in Enterprise SAP BTP
Your have now logged on to your enterprise SAP Business Technology Platform landing page.
Follow the following steps to access the free SAP Business Technology Platform trial account.
1. On your enterprise SAP Business Technology Platform landing locate and select the
Trial Home button.
2. The rest of the creation and log on procedure is identical to the, previously explained,
personal SAP Business Technology Platform Trial procedure.
What is in Scope for SAP HANA Cloud and SAP BTP Trial
The SAP HANA Cloud is part of the SAP Business Technology Platform, so you will not only be
able to explore the SAP HANA Cloud features, but also the complete feature set of the SAP
Business Technology Platform trial.
● You can use productive and beta services. To consume beta services, you must enable the
sub-account for beta features.
● You can manage members in your trial account.
● A trial account includes 4 GB of memory for applications.
● You can use 8 GB of instance memory.
● There are 10 total routes and 40 total services available.
● You can use 2 configured on-premise systems with the Cloud Connector.
● There’s no service level agreement with regards to the availability of the platform.
● You can use HDI containers in a shared SAP HANA database (only available a few regions).
Caution:
In the trial account, the SAP HANA Cloud, SAP HANA database instance and SAP
Business Technology Platform applications and services are stopped every day
at midnight (or some time thereafter depending on server load) relative to the
region in which you created your trial account. If you’re working in a time zone
that is far from the region where you trial account was created, then your
applications may stop during business hours.
Summary
In this lesson, you have gained insight in which services and features SAP HANA Cloud and
SAP BTP are provide in the trial environments. You have also learned how to log on to your
SAP BTP trial or enterprise SAP BTP account.
LESSON SUMMARY
You should now be able to:
● Log-in using the SAP BTP Cockpit
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Log-in using the Cloud Foundry CLI
The details on how to use the Cloud Foundry CLI commands will be explained the respective
lessons.
Note:
Please only download from trusted sources.
2. Use the following command to download and add the Cloud Foundry Foundation public
key to your system:
wget -q -O - https://packages.cloudfoundry.org/debian/
cli.cloudfoundry.org.key | sudo apt-key add
Note:
In this step you will be asked to provide your OS password
3. Use the following command to add the package repository to your system:
echo "deb https://packages.cloudfoundry.org/debian stable main" | sudo
tee /etc/apt/sources.list.d/cloudfoundry-cli.list
4. Use the following command to update your local package manager information:
sudo apt-get update
You now have installed the Cloud Foundry CLI on your local desktop computer.
2. Log on to the SAP BTP Cloud Foundry environment with the command:
A list with the available API Endpoint URLs can be found here: Available API Endpoints
To get a detailed overview of how to use a specific command use the command:
cf help [command]
Example:
cf help services
NAME:
services - List all service instances in the target space
USAGE:
cf services
ALIAS:
s
OPTIONS:
--no-apps Do not retrieve bound apps information.
SEE ALSO:
create-service, marketplace
Example:
cf service HC200-Trial-Database
When using the Cloud Foundry CLI you often need to specify the technical name of the service
offering and the service plan. The entitled service offering in your account can be found in the
SAP BTP Service Marketplace as shown the above figure.
It's also possible to retrieve the technical names of the service offerings and service plans
using the Cloud Foundry CLI. Use the cf marketplace command to list the service offering
and Service plans as shown in the above figure.
A service plan describes a particular service (for example, a database configuration) that is
available for use. Service brokers advertise their service plans onto a catalog. You can use
these advertised service plans to configure a particular service you want to create.
Summary
In this first part lesson you have learned how to download and install the Cloud Foundry CLI.
Next you learned how to lon on to the SAP BTP using the Cloud Foundry CLI. You also learned
the basics on how to use the tool and it's embedded documentation of the CLI command set.
LESSON SUMMARY
You should now be able to:
● Log-in using the Cloud Foundry CLI
Learning Assessment
1. When you create a personal account on SAP.com, your profile visibility is set to Public.
Choose the correct answers.
X A True
X B False
X A E-mail address
X B Credit-card number
X C Telephone number
X D Home address
3. When you have an SAP BTP enterprise account it is not possible to have a free SAP BTP
trial account.
Determine whether this statement is true or false.
X True
X False
4. With which command can you find the name of the SAP HANA Cloud database service?
Choose the correct answer.
X C cf services
Lesson 1
Deploying a SAP HANA Cloud Database Instance 44
Exercise 3: Create a SAP HANA Cloud Database Instance 55
Lesson 2
Introducing the Storage Options in SAP HANA Cloud 59
Lesson 3
Adding a Data Lake to your SAP HANA Cloud Database 64
Exercise 4: Add a Integrated Data Lake 69
Lesson 4
Adding a standalone Data Lake to SAP HANA Cloud 72
Exercise 5: Add a Standalone Data Lake 79
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Deploy a SAP HANA Cloud Database
Business Case
As a database administrator, you want to deploy a SAP HANA Cloud database instance in the
BTP trail to explore the SAP HANA Cloud capabilities. Your BI modeling colleagues will use
this database to learn how they can build their analytic reports.
Use the following path to navigate from the trial SAP BTP Cockpit to the SAP HANA Cloud
area:
● On the SAP BTP Cockpit Global Account page, select the trial subaccount in the
Subaccounts area. Next on the Subaccount: trial - Overview page, select the dev space in
the Spaces area. The breadcrumbs area (1) shows your location in the SAP BTP.
● On the Space: dev - Applications page, in the menu panel select the SAP HANA Cloud (2)
button.
On the SAP HANA Cloud overview page you get an overview of the status of all your SAP
HANA Cloud, SAP HANA Database instances. In the trial SAP BTP account you can only
create one SAP HANA Cloud, SAP HANA Database instance. In an enterprise SAP BTP
account the number of database instances depends on your entitlements in the license
agreement with SAP.
● To open the SAP HANA Cloud Central where you can create a new SAP HANA Cloud, SAP
HANA Database instance select the Manage SAP HANA Cloud (3) button.
The SAP HANA Cloud Central is the place to provision and manage your SAP HANA Cloud
instances. In a new SAP BTP account the SAP HANA Cloud Central is empty, but with the
Create (1) button you can start the Create Instance Wizard and deploy your first SAP HANA
Cloud instance.
In the first step of the Create Instance Wizard, you need to decide which type of instance you
want to create. The following options are available:
● SAP HANA Cloud, SAP HANA Database provides an in-memory and multi-model database
system to store and analyze relational but also document data which allows for real-time
data analytics and transactional processing in one combined system. The in-memory
database can handle OLAP and OLTP workloads, setup hybrid Extension to on-premise
SAP HANA systems and can be associated with a data lake instance.
● SAP HANA Cloud, Data lake SAP HANA data lake efficiently and securely stores, manages,
and analyzes large amounts of structured, semi-structured and unstructured data. The
data lake instance manages access to files in the data lake through Files component and
can be used for high performance analysis on petabyte volumes of relational data with
HANA Cloud, data lake Relational Engine.
Caution:
In this learning material the steps to create a SAP HANA Cloud, SAP HANA
Database will be explained. The follow-up steps for the other choices will be
different.
In the step you need to provide the location, instance name, description and the administrator
password.
● In the (1) Location area you need to fill-in the location space, which is the Cloud Foundry
Organization name and the Cloud Foundry Space name. If your company has multiple
Organizations and Spaces created for different projects, then select the correct
Organization and Space from the drop-down menus.
Note:
In the SAP HANA Cloud Trial, the organization and the space were created
during the automated setup procedure.
● In the Basics area you need to specify the database instance name and description of the
SAP HANA database instance you want to create. An instance in SAP HANA Cloud is like a
tenant for a on-premise SAP HANA database and isn't restricted to 3 characters.
You also need to specify the password for the database administrator user account
DBADMIN that will be created and assigned to your SAP BTP account. The password need
to be at least 8 characters long, with one UPPER and two lower case letters and one
number.
There is no SYSTEM user available, you need to use the DBADMIN user for the initial setup
tasks. The DBAMIN is the "super" user for your SAP HANA Cloud, SAP HANA Database
instance. This user shouldn't be used on a daily basis. Create new user accounts and roles for
all users accessing the database.
Specify the required RAM and disk storage (1) for this SAP HANA Cloud database instance.
The number of vCPUs depends on the amount of RAM you specify.
In the SAP BTP trial account you can't change the size of the memory and disk storage
allocated to the database instance. This is limited to 30 GB RAM and 120 GB disk space.
A SAP HANA Cloud, SAP HANA Database instance in an enterprise SAP BTP account can
allocate up to 5790 GB RAM, 16000 GB disk space and 440 vCPUs.
Note:
The required disk space and virtual CPUs (vCPUs) can't be changed manually, but
are automatically assigned to the database instance. The amount of disk space
and vCPUs depends on the assigned RAM.
In this step, you can specify which (1) Availability Zone you want to use. The availability zone
can be set automatically, or you can choose your zone manually.
The supported memory size varies by availability zone. If the availability zone in which you
want the instance placed is not selectable from the list, lower the memory size of the instance.
Keeping the setting to automatic will make sure that the best zone for your database size and
performance is selected.
You can also setup (2) replica databases of your SAP HANA database instance. A replica
database is used to improve the availability of your SAP HANA database instance. A replica
database is automatically kept up to date during normal operations and if a takeover is
required it will be performed automatically.
You can setup maximum of 2 replicas for SAP HANA Cloud. One synchronous replica in the
same availability zone, and one asynchronous replica in a different availability zone.
Caution:
Adding additional replicas to your instance incurs additional costs based on the
size (CPU, memory, disk) of the replica database. You can use the SAP HANA
Cloud Capacity Unit Estimator to estimate the number of capacity units per
month required for your particular use case. Link to the SAP HANA Cloud
Capacity Unit Estimator
In the SAP HANA Database Advanced Settings step, you can setup some additional features.
In the (1) Allowed Connections area, you can choose which IP addresses are allowed to
connect to your SAP HANA Cloud database instance.
Animation
For more information on this topic please view the animation in the lesson
Deploying a SAP HANA Cloud Database Instance in your online course.
● Allow specific IP addresses and IP ranges. Use this option when there should be only
access possible from your corporate network.
Note:
In the SAP HANA Cloud Central, you can use the Edit option in the Actions menu
to activate the cloud connector after the SAP HANA Cloud database instance was
deployed.
The Cloud Connector provides the following features for business-critical enterprise
scenarios:
● Automatic recovery of broken connections.
● Audit logging of inbound traffic and configuration changes.
● High-availability setup.
In the enterprise SAP BTP account, you can also add a SAP HANA Script server and a SAP
HANA Document Store as additional features to the SAP HANA database instance. When
adding these features to a SAP HANA database instance may require more vCPUs (compute)
and increase your licensing cost.
In the 6th and final step of the Create Instance Wizard you can decide to add an integrated
data lake instance to your SAP HANA database instance. This integrated data lake allows you
to ingest, store, and analyze high volumes of data, economically and securely. You can access
and manage the integrated data lake from your SAP HANA database.
Integrated SAP HANA Data Lake
The Integrated SAP HANA Data Lake gives you the option to store the older and rarely used,
but still important, cold data in a data lake controlled by the SAP HANA database instance.
This database instance already stores your hot data in memory and the warm data in the SAP
HANA Native Storage Extension (NSE). With the addition of a data lake to the SAP HANA
Cloud database instance you have access to all your data from one single framework.
The SAP HANA Cloud database instance is being created. Refresh the screen every few
minutes to see an updated status.
What is setup during the creation process of SAP HANA Cloud, SAP HANA database:
● A SAP HANA database instance is created with data at rest encryption enabled.
● The SAP HANA database instance is connected to SAP HANA cockpit.
● The SAP HANA database instance is connected to SAP HANA database explorer.
● The database user DBADMIN is created for administration purposes.
● The SAP HANA database is connected to backup infrastructure via the Backint interface.
● A backup cycle of 15 backup generations is setup, and the initial backup is created.
As soon as all these tasks are performed the SAP HANA Cloud, SAP HANA trial database is
available for you to explore.
To create an SAP HANA Cloud database using the Cloud Foundry CLI execute the following
steps:
Note:
If you use the SAP HANA Cloud trial account with one organization and space
you can omit the -o, -s and -a options.
Example:
cf create-service hana-cloud hana HC200-Trial-Database -c '{ "data":
{"memory": 32, "systempassword": "Welcome1"}}'
The above command will create a database service named HC200-Trial-Database with
32GB memory and the DBADMIN user will get the password Welcome1.
Note:
In an SAP HANA Cloud trial account you can only create a 30GB database
instance.
Have a look at the Create an SAP HANA Database Instance Using the CLI page to have a
complete list of parameters that can be used to create a database instance.
Summary
In this lesson, you have learned how to deploy a SAP HANA Cloud database instance using the
SAP BTP and Cloud Foundry CLI.
Simulation
For more information on this topic please view the simulation in the lesson
Deploying a SAP HANA Cloud Database Instance in your online course.
Simulation
For more information on this topic please view the simulation in the lesson
Deploying a SAP HANA Cloud Database Instance in your online course.
LESSON SUMMARY
You should now be able to:
● Deploy a SAP HANA Cloud Database
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Describe the different SAP HANA Cloud Storage Options
Data tiering in SAP HANA Cloud gives you a cost-effective storage solution, which allows you
to assigning data to different storage and processing tiers so that you can fulfill your data
management strategies.
Animation
For more information on this topic please view the animation in the lesson
Introducing the Storage Options in SAP HANA Cloud in your online course.
In SAP HANA Cloud you can split data between different temperature tiers: hot, warm, and
cold. As the data’s value changes, you can move it between each tier.
● Hot data: It is often changed and stored in-memory. Hot storage is ideal for frequently
changed data that is used for real-time processing and analytics. In SAP HANA Cloud, hot
data is both the highest performance and highest TCO storage option.
● Warm data: It is less frequently changed and therefore stored on disk, which in SAP HANA
Cloud is the Native Storage Extension (NSE). Warm data isn’t fully loaded into memory, so
this option is more cost-effective than hot data but still has very low latency. It’s best for
data that doesn’t need to be accessed frequently.
● Cold data: It is not accessed often and therefore can be located in cold storage. This cold
data is managed separately from the SAP HANA Cloud database but can still be accessed
by using the data virtualization capabilities. In SAP HANA Cloud, we recommend that you
store cold data in the integrated data lake. This combines the massive storage capacity of
a data lake – up to the petabyte scale – while keeping it all within a structure that simplifies
and accelerates data analysis. The SAP HANA Cloud relational data lake ensures that
applications can rapidly access data despite massive data volumes.
SAP HANA native storage extension is integrated with other SAP HANA functional layers,
such as query optimizer, query execution engine, column store, and persistence layers. The
key highlights of the SAP HANA native storage extension include the following:
● A substantial increase in SAP HANA data capacity, with good performance for high-data
volumes.
● The ability to co-exist with the SAP HANA in-memory column store, preserving SAP HANA
memory performance.
● An enhancement of existing in-market paging capabilities by supporting compression,
dictionary support, and partitioning.
● An intelligent buffer cache that manages memory pages in SAP HANA native storage
extension column store tables.
● The ability to monitor and manage buffer cache statistics via system views.
● The ability to support any SAP HANA application.
● A simple system landscape with high scalability that covers a large spectrum of data sizes.
This is where the SAP HANA Cloud data lake can be very effective. It’s a data lake that can
reach a petabyte scale, as well as store structured and unstructured data. This makes sure
that you can store the data without structuring it first and then use it for analytics, if
necessary. Built on SAP Relational Engine, the data lake provides excellent performance for
analytics across large volumes of data. With the SAP HANA data lake, you avoid the risk of
creating an uncontrollable, unusable data dump.
The data lake in SAP HANA Cloud is integrated, but at the same time independent from the
SAP HANA database when it comes to storage and compute. In SAP HANA Cloud, you can
choose to use a data lake related to each SAP HANA Cloud instance you create. It’s a simple
click that allows you to enable a data lake in your instance, either when you first create it or
later, as needed . You can also take advantage of cloud elasticity to scale your data lake
storage and compute up or down whenever necessary.
For the initial release of SAP HANA Cloud, a data lake starts with 1TB of storage size and can
go up to 90 TB, in 1TB increments. The maximum compute capability of a data lake is 162
vCPU. To access your data lake, you can use the existing SAP HANA tools, like the Database
Explorer. The data lake can support ingestion of data from object storage locations (e.g.,
Azure blob store, Amazon S3) at a rate of 1TB per day per dedicated vCPU per table, up to a
maximum of 16TB per day per table.
Another important point is that the SAP HANA Cloud data lake inherits the security and data
protection available for all of your instances of SAP HANA Cloud automatically, without any
action needed from you.
Summary
In this lesson, you have learned which Data tiering options are available in SAP HANA Cloud
and learned about SAP HANA Cloud, Native Storage Extension (NSE) and the integrated SAP
HANA Cloud, Data Lake.
LESSON SUMMARY
You should now be able to:
● Describe the different SAP HANA Cloud Storage Options
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Add an Integrated Data Lake to the SAP HANA Cloud Database
Business Case
See the following video to know the Business Case for adding an integrated Data Lake.
The BI reporting team needs a Data Lake added to the existing SAP HANA Cloud, SAP HANA
database instance in order to store the huge amounts of sensor data where they need to
report on.
As a database administrator, you want to deploy a SAP HANA Cloud, Data Lake instance
attached to the SAP HANA Cloud, SAP HANA database that is already used in the SAP BTP
trial as this is the most cost efficient method. Your BI modeling colleagues will use this data
lake to learn how they can build their analytic reports.
Use the following path to navigate from the trial SAP BTP Cockpit to the SAP HANA Cloud
area:
● On the SAP BTP Cockpit Global Account page, select the trial subaccount in the
Subaccounts area. Next on the Subaccount: trial - Overview page, select the dev space in
the Spaces area. The breadcrumbs area (1) shows your location in the SAP BTP.
● On the Space: dev - Applications page, in the menu panel select the SAP HANA Cloud (3)
button.
● To manage your SAP HANA databases and data lakes instances select the Manage SAP
HANA Cloud (3) button.
The SAP HANA Cloud Central app gives you an overview of all your databases. You are able to
see the status of all databases, and can also perform database administration tasks like e.g.
start/stop, upgrade, or adding a integrated data lake. The security settings allow you only to
see the databases where you have the permissions to access them.
The SAP HANA Cloud Central opens in a new browser tab. This makes it easier to navigate
between the SAP HANA Cloud Central and SAP BTP Cockpit.
Press the °°° (2) button to open the Actions Menu for the selected cloud database. From the
Actions Menu select the Add Data Lake (3) option.
In the Create Data Lake Instance wizard, you need to specify the Data Lake instance name
and Description in the Basics area. You also need to enter and confirm a strong password.
Note:
The user HDLADMIN is automatically created and assigned to you for data lake
administration tasks.
In the Sizearea of the input screen, you can specify the number of vCPUs for the Compute and
Storage nodes. The minimal required number of vCPUs is calculated from the storage size. In
the trial account the storage size is fixed, so you have to accept the given number of vCPUs.
Note:
In an enterprise SAP BTP account, you can also select the Storage Service Type.
You can choose between SAP Native Data Lake files and AWS Elastic File System
(EFS). In the trial account this is fixed to the AWS Elastic File System (EFS) and
cannot be changed.
In the Connections area you specify which IP addresses are allowed to connect to your data
lake instance. Depending on your need you keep the connections local to the SAP BTP, or only
specific IP addresses and ranges of your company or all IP addresses.
Caution:
The option Allowing all IP addresses means that your data lake exposes to the
whole internet!!
Summary
In this lesson, you have learned how to attach a SAP HANA data lake instance to an existing
SAP HANA database in your SAP BTP trial account.
Simulation
For more information on this topic please view the simulation in the lesson
Adding a Data Lake to your SAP HANA Cloud Database in your online course.
Simulation
For more information on this topic please view the simulation in the lesson
Adding a Data Lake to your SAP HANA Cloud Database in your online course.
LESSON SUMMARY
You should now be able to:
● Add an Integrated Data Lake to the SAP HANA Cloud Database
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Add a Standalone Data Lake to the SAP HANA Cloud
Business Case
See the following video to know the Business Case for adding an standalone Data Lake.
The BI reporting team needs a Data Lake added to the existing SAP HANA Cloud in order to
store huge amounts of unstructured data that use to enhance the structured data in the SAP
HANA Cloud database instance.
As a database administrator, you want to deploy a standalone SAP HANA Cloud, Data Lake
instance to the SAP HANA Cloud as this is the most cost efficient method to store the
unstructured data. Your BI modeling colleagues will use this standalone data lake to learn how
they can enhance their analytic reports with the unstructured data in the standalone data
lake.
You can easily add a standalone data lake to your SAP HANA Cloud using the SAP HANA
Cloud Central overview page. On the SAP HANA Cloud Central overview page press the
Create (1) button to start the Create Instance Wizard and deploy a SAP HANA Cloud, Data
lake instance.
In the first step of the Create Instance Wizard, you need to decide which type of instance you
want to create. In this example, select the SAP HANA Cloud, Data lake (2) option. After the
instance type selection, continue with the Next Step (3).
In the General - Basics area you need to specify the instance name and description of the data
lake you are going to create. You also need to specify who is allowed to connect to your
integrated data lake. The options are:
● Allow only BTP IP addresses. This is the most secure option, but this also means the data
lake can only be access from applications inside the SAP BTP environment. No
connections to the outside world.
● Allow all IP addresses. This option allows a connection from every IP address in the whole
world. This option is only suitable if you have a public service that needs to be accessible
from anywhere in the world.
● Allow specific IP addresses and IP ranges (in addition to BTP). This option allows you to
specify your companies IP addresses or IP ranges. With this option your employees from
the corporate network can access the data lake in the SAP BTP.
After specifying the Basics and Connection information, continue with the Next Step (3).
In the Create Instance - data lake Relational Engine step you enable the data lake Relational
Engine. If you enable data lake Relational Engine, you can use the data lake to ingest, store,
and analyze high volumes of date in a disk based database. If you don't enable data lake
Relational Engine you only get a file based data lake with limited capabilities.
In the Size area you can specify how many vCPUs will be allocated for the Coordinator and the
Workers, the number of vCPUs for the Compute instance is calculated from the number of
vCPUs for the Coordinator and the Workers. You can also specify how many Workers should
be created.
For the data lake Relational Engine option, you also need to provide a strong password for the
database administrator (HDLADMIN).
In the Create Instance - data lake Relational Engine Advanced Settings (optional) step you
specify if the data lake need to maximally compatible with SAP HANA or SAP Relational
Engine. Which option you choose depends on the applications you want to connect to the data
lake and what their preference is. Also if you develop you own applications on top of the data
lake, then the developers knowledge of SAP HANA or SAP Relational Engine would be the
decisive factor.
If you decide to use SAP Relational Engine, then you can some general options that are
specific to SAP Relational Engine. the options are:
● A Collation describes how to sort and compare characters from a particular character set
or encoding. You can choose from 30+ different collations.
● If you require, then the Case Sensitivity can be switched on or off for collations.
● For the NChar data type you can also specify the collation to use. Here you can choose
between UTF8BIN and UCA.
Note:
The NCHar data type stores Unicode character data
● The NChar Case Sensitivity behaviour con be specified as well. The options are ignore,
respect, UpperFirst of LowerFirst.
The SAP HANA Cloud, Data Lake is being created and started.
In the SAP HANA Cloud Central you can see the difference between a SAP HANA Cloud, Data
Lake (standalone data lake) and an integrated data lake attached to SAP HANA Cloud, DAP
HANA database.
The standalone data lake is represented under its own header with the data lake instance
name as you specified.
The integrated data lake is represented under the header of the SAP HANA database it is
associated with.
Summary
In this lesson, you have learned how to create a standalone SAP HANA data lake instance and
how to distinguish between the integrated and standalone data lakes in SAP HANA Cloud
Central.
LESSON SUMMARY
You should now be able to:
● Add a Standalone Data Lake to the SAP HANA Cloud
Learning Assessment
1. In the SAP BTP trial account, you can freely define the memory, compute and storage size
as long as you stay below 30 GB memory, 2 vCPUs compute units and 120 GB of storage.
Choose the correct answer.
X A True
X B False
2. The SAP HANA Native Storage Extension option is enabled by default in the SAP HANA
Cloud, SAP HANA database instance.
Choose the correct answers.
X A True
X B False
3. Which attributes can you specify when attaching an integrated data lake to an excising
SAP HANA Cloud database?
Choose the correct answer.
4. Which service types are used in a standalone SAP HANA Cloud Data Lake?
Choose the correct answers.
X A Compile
X B Coordinator
X C Worker
X D Name
Lesson 1
Opening SAP HANA Cockpit 86
Exercise 6: Open SAP HANA Cockpit 89
Lesson 2
Alerting Cards in SAP HANA Cockpit 92
Exercise 7: Use the Alerts Card 97
Exercise 8: Use the Alert Configuration 101
Lesson 3
Monitoring Resources in SAP HANA Cockpit 104
Exercise 9: Use the Services Card 109
Exercise 10: Use the Performance Monitor Card 117
Exercise 11: Use the Monitor Table Usage Card 123
Lesson 4
Monitoring SQL Workload in SAP HANA Cockpit 126
Exercise 12: Use the Sessions Card 129
Exercise 13: Use the Threads Card 135
Exercise 14: Use the SQL Statement Card 141
UNIT OBJECTIVES
● Open the SAP HANA Cockpit for SAP HANA Cloud databases
● Use the SAP HANA Cockpit alerting cards
● Use the SAP HANA Cockpit resource monitoring cards
● Use the SAP HANA Cockpit system load monitoring cards
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Open the SAP HANA Cockpit for SAP HANA Cloud databases
Business Case
As a database administrator of the SAP HANA Cloud database, you need to use the SAP
HANA cockpit to administer the SAP HANA Cloud databases deployed in the SAP Business
Technology Platform.
Navigate from the Trial home page to your dev space (1) where you will find the SAP HANA
Cloud. Click the SAP HANA Cloud (2) button to get an overview of the available SAP HANA
Cloud database instances.
To administer your SAP HANA Cloud database instance, press the Manage SAP HANA Cloud
(3) button. This will open the SAP HANA Cloud Central where you get a detailed overview of
all the SAP HANA Cloud databases managed by you.
The SAP HANA Cloud Central opens in a new browser tab. This makes it easier to navigate
between the SAP HANA Cloud Central and SAP BTP Cockpit.
Press the °°° (2) button to open the Actions Menu for the selected cloud database. From the
Actions Menu select the Open in SAP HANA cockpit (3) option.
The SAP HANA cockpit - Overview page opens in a new tab and displays a set of card that can
be used to monitor the SAP HANA Cloud database instance.
Note:
SAP HANA Cloud database instances can only be administrated by the SAP HANA
cockpit provided in the SAP BTP.
Use the Search (2) field to quickly find the monitoring card you need. Many card display, in
real-time, in a mini chart monitoring data that represents their function. As an example show
in the above screenshot you see the CPU Usage (3) card. The mini chart show the Total CPU
usage of your SAP HANA Cloud database instance.
Summary
In this lesson, you have learned how to open the SAP HANA cockpit available in the SAP
Business Technology Platform.
LESSON SUMMARY
You should now be able to:
● Open the SAP HANA Cockpit for SAP HANA Cloud databases
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Use the SAP HANA Cockpit alerting cards
Business Case
As an administrator, using the alerting framework, you can proactively monitor the status of
the SAP HANA Cloud database instance. With the alerting framework you are alerted to
critical situations, for example: a disk is becoming full, CPU usage is reaching a critical level,
or a server has stopped.
The internal monitoring infrastructure of the SAP HANA database is continuously collecting
and evaluating information about status, performance, and resource usage from all
components of the SAP HANA database. In addition, it performs regular checks on the data in
system tables and views and when configurable threshold values are exceeded, it issues
alerts. In this way, you are warned of potential problems. The priority of the alert indicates the
severity of the problem and depends on the nature of the check and the configured threshold
values. For example, if 90% of available disk space has been used, a low priority alert is
issued; if 98% has been used, a high priority alert is issued.
In the SAP HANA cockpit - Database Overview page, search for the Alerts card (1).
The Alerts card (2) shows the current alerts of the SAP HANA Cloud database. Multiple alerts
can be shown. Their status can be High or Medium depending of the severity of the detected
problem.
Clicking on the Alerts card opens the Alerts app (3) which gives a detailed breakdown of all
the current alerts in your SAP HANA Cloud database.
On the Manage Alerts page, the default summary list includes all current alerts with a priority
of high, medium, and error. You can filter, sort, and view details in the search area (1) as
needed.
In the Alerts display area (2) you see detailed information on the available alerts. The columns
provide the following information.
● Priority - Indicates the severity of the alert and how quickly action needs to be taken. The
following priorities are possible:
- Information - Action is recommended to improve system performance or stability.
- Low - Medium-term action is required to mitigate the risk of downtime.
- Medium - Short-term action is required (few hours, days) to mitigate the risk of
downtime.
- High - Immediate action is required to mitigate the risk of downtime, data loss, or data
corruption.
- Error - Immediate action is required to fix the issue. Use trace files to help track and
resolve the issue.
● Alert - Provides a description of the alert.
● Time - Indicates the time that the alert was triggered.
● Alerting Host & Port - Provides the name and port of the host that issued the alert.
● Source - Indicates where the alert originated from.
● Category - Indicates the category of the alert checker that issued the alert. Alert checkers
are grouped into categories. The categories are:
- Availability
- Backup
- Configuration
- CPU
- Diagnosis Files
- Disk
- Memory
- Other
- Security
- Sessions/Transactions
Click on alert to see its definition and more details, such as past occurrences, proposed
solutions, and next scheduled runs.
Animation
For more information on this topic please view the animation in the lesson
Alerting Cards in SAP HANA Cockpit in your online course.
On the alert definition page, you get full details on the alert text and trigger time, source, alert
definition, proposed solution and the number of occurrence over time.
1. Check Now: This button let's you re-run the alert checker. In some cases, you may want to
check for a particular alert outside of its configured schedule. Running an alert definition on-
demand doesn’t change its next configured interval to run. An alert definition must have an
active status to run it manually.
2. Edit Alert Definition: This button allows you to tailor the alert definitions in the SAP HANA
database to your needs.
3. Details: This tab displays the full alert text to better understand the possible cause of the
alert, also it gives the exact time stamp when the alert was triggered and the origin of the
alert. The source could be the database itself, or a service such as the SAP EarlyWatch Alert
service.
4. Alert Definition Details: This tab displays full details about the alert definition, when the next
scheduled run is planned and the schedule interval.
5. Proposed Solution: It gives a possible solution to correct the error that triggered this alert.
The solution is provided by SAP and will often include a SAP Note that explains the solution in
more detail.
6. Occurrences: This tab gives a graphical representation of all the occurrences of the
selected alert over time. The time period to display the occurrences is by default 24 hrs, but
can be changed to 7 or 30 days. This overview can be very useful to find the exact moment in
time the alerts started to appear. Knowing this moment could help to identify the cause of the
alert.
Summary
In this lesson, you have learned how to use the alerting framework available in the SAP HANA
cockpit provided in the SAP BTP.
The Alerts in the SAP HANA Cloud database instance come with default threshold values and
repeat intervals. Customize the threshold values to your own companies standards. In this
way the SAP HANA Cloud database complies to the same monitoring standards as the on
premise databases.
In the SAP HANA cockpit - Overview page search for Alert Definitions. The Alert card is found
that has a link Alert Definitions. Open the Alert Definitions app by clicking the link.
Hint:
Alternatively, you can use the Alert Definitions link in the Alerting and Diagnostics
card.
Use the search (2) fields to quickly find the alert you need to customize. You can search via:
● Status - Display the Alert status (Active, Inactive)
● Last Run - Show alerts that ran never, or in the last 2, 10 or 120 minutes.
● Category - Alerts that belong together are grouped in categories. The following categories
exist Availability, Backup, Configuration, Diagnosis Files, Disk Memory, Other Security and
Session/Transactions.
● Source - Alters can originate from different sources like e.g. SAP HANA database
A list of available alerts is shown. Select a Alert Definition (3) to open the Alert Definition
details.
See the following video for changing the Alerts Definition properties.
In the Alert Definition details page you enter the change mode by clicking the Edit button. In
the change mode you can adapt the following settings:
Threshold values (1) - Depending on the KPI connected to the Alert, you can set Low, Medium
and High values. When the KPI goes above or below these Threshold values the an Alter is
triggered. For alert that can have values successful or unsuccessful e.g. backups you can
setup thresholds values.
Schedule Active (2) - You can enable or disable a alert checker. Disabling a alert checker
doesn't fix the problem, it only stops the testing of the threshold values for this alert by the
alerting system. This doesn't mean that there are no problems, it only means that the altering
system will not inform you about possible problems in that specific area.
Summary
In this lesson, you have learned how to change the alert attributes provided in the alerting
framework available in the cloud version of the SAP HANA cockpit.
LESSON SUMMARY
You should now be able to:
● Use the SAP HANA Cockpit alerting cards
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Use the SAP HANA Cockpit resource monitoring cards
Business Case
As an database administrator, you want to monitor the availability and resource consumption
of the SAP HANA Cloud database services.
In the SAP HANA cockpit - Database Overview page, search for the Services card (1).
The Services card (2) shows the status of the SAP HANA Cloud database. The status can be,
for example, running, running with issues, or stopped.
Clicking on the Service card opens the Manage Services app (3) that gives a detailed
breakdown of the status of all SAP HANA Cloud services.
The Manage Services app gives you an (1) overall status summary of your database.
The Reset Memory Statistics button (2) lets you clear the statistics history.
Peak used memory is the highest recorded value for used memory since the last time the
memory statistics were reset. This value is useful for understanding the behavior of used
memory over time and under peak loads. Resetting peak used memory allows you, for
example, to establish the impact of a certain workload on memory usage. If you reset peak
used memory and run the workload, then you can then examine the new peak used memory
value.
The Go to Alerts button (3) lets you directly open the Alerts application to investigate the
alerts associated to this resource.
The Kill Service button (4) stops the selected service immediately and if the related option is
selected, creates a crash dump file. Normally the SAP HANA daemon will restart the killed
service.
The Settings icon (5) lets you add and remove columns from the display. Not all columns are
visible by default.
The Service column (1) show the service name, for example, indexserver, nameserver,
xsengine, and so on
The Status column (2) show the The status of the service. The following statuses are possible:
● Running - the service is operating within normal parameters.
● Running with Issues - at least one service is not running, or there is at least one high alert.
● Starting - the service or system is starting.
● Stopping - the service or system is stopping.
● Stopped - the service is stopped.
● Not Running - to investigate why the service is not running, you can navigate to the crash
dump file created when the service stopped.
The Role column (2) shows the role of the service in a failover situation. Currently not
applicable in SAP HANA Cloud.
The Port column (3) show the port number that the system uses for internal communication
between services
The Process ID column (4) show the operating system process id assigned to this service.
The CPU column (5) displays a mini chart visualizing the CPU usage of the service. Choosing
the mini chart opens the Performance Monitor app for a more detailed breakdown of CPU
usage.
The Memory column (6) provides a mini chart visualizing the memory usage of the service.
The different colors represent the following:
● Dark green shows the service's used memory.
● Light green shows the service's peak memory.
● The grey stroke represents the effective allocation limit.
Choosing the mini chart opens the Memory Analysis app for a more detailed breakdown of
memory usage.
The SQL Port column (7) show the SQL port number assigned to this service. Not all services
require an SQL port.
Selecting the mini chart in the CPU Column (1), the Performance Monitor app is opened and
displays a detailed breakdown of CPU usage over time.
Clicking the Memory column (2) mini chart opens the Memory Analysis app for a more
detailed breakdown of memory usage.
The applications Performance Monitor and Memory Analysis will be explained in detail in their
respective SAP Learning Card.
Summary
In this lesson, you have learned how to monitor the SAP HANA Cloud database services using
the SAP BTP version of the SAP HANA cockpit.
In the SAP HANA cockpit - Database Overview page, search for the Monitoring Performance
app (1).
The Monitoring card (2) shows several links to useful monitoring applications like the Monitor
Performance and the Monitor Table Usage app.
Clicking on the Monitor Performance link opens the Performance Monitor app which, by
default, gives a detailed breakdown (3) of several important resources (CPU, memory,
transactions and threads) of the SAP HANA database over a time frame of the last hour.
Monitoring the performance of your SAP HANA database is important. Performance can be
measured on the basis of memory, CPU and disk. All these KPIs are important and could be
used to investigate possible performance issues.
To make the data as insightful as possible, the SAP HANA cockpit provides three cards that
display a mini graph on their specific KPI (memory, CPU, and disk). All three cards open the
Performance Monitor, but will immediately focus on their respective KPI.
Animation
For more information on this topic please view the animation in the lesson
Monitoring Resources in SAP HANA Cockpit in your online course.
The Memory Usage card lets you switch between a summary of used and resident memory.
When you move your mouse over the summary graph, a category breakdown appears.
The CPU Usage card shows you the current CPU load on your SAP HANA database instance.
The Disk Usage card show you the total disk usage and a breakdown into the important disk
areas of Data, Log and Trace. The card also indicated when a file system runs out of space.
Hint:
All the features shown in the following screen shots are part of the Performance
Monitor app and are independent from the selected resource memory, CPU or
disk.
The Performance Monitor opens displaying the load graph for the selected resource: CPU,
disk, or memory. The load graph initially visualizes resource usage of all hosts and services
listed on the left according to the default KPI group of the selected resource.
By default the Performance Monitor app show the measurement values of the selected
resource from the last hour.
Defining the monitored time frame (1) by entering your desired dates or selecting form
Presets (2). The following presets are available:
● Last 5, 15, or 30 Minutes
● Last 1, 3, 6, 12 or 24 hours
● Last 2 or 7 days
● Today, this day last week, yesterday, day before yesterday
● This week, previous week or this month
Note:
Using the auto refresh button, you can set the auto refresh rate between every 10
seconds to every 10 minutes.
Using the My View (1) drop down menu to quickly switch between the different resources. The
four default views (CPU, Memory, Disk and Default) can be used, but you can also create and
save your own views with the monitoring KPIs of your choice.
Using the manage configurations (2) button allows you to select your own KPIs.
In the Add and Remove KPIs pop-up window, you can select from which services you want to
see the selected KPIs measurement data. You can also select several on host level
aggregated KPIs values.
Create a complete snapshot of the current performance monitor data by exporting the
monitoring views data into the a LOAD_HISTORY.zip file. The content of the following system
views will be exported:
● SYS.M_LOAD_HISTORY_INFO
● SYS.M_LOAD_HISTORY_HOST
● SYS.M_LOAD_HISTORY_SERVICE
● SYS.M_DATABASE
● SYS.M_SERVICES
Summary:
In this lesson, you have learned about the different features available in the Performance
Monitor app in SAP HANA cockpit.
In the SAP HANA cockpit - Database Overview page, search for the Monitoring (1).
The Monitoring card (2) shows several links to useful monitoring applications like the Monitor
Table Usage app.
Clicking on the Monitor Table Usage link opens the Table Usage app which, by default, gives a
detailed bubble chart Top 50 (3) of the table usage by read and write access.
Monitor table activity to identify where you can improve performance and reduce memory
utilization. Large in-memory tables that are accessed infrequently are good candidates for the
SAP HANA Cloud, Data Lake option.
Use the Go to Alerts (1) button to see if exceptional large table with very high read/write
access cause alerts in your SAP HANA Cloud database.
Filter Tables (2) allows you to filter by the number of times a table is accessed and the table
size. You can also specify how many tables you want to see in the listing.
The bubble-chart and table-chart buttons (3) let you switch between the graphical view and
the list view.
In the Filter Tables (1) select options field, you can combine all the filter options. This means
you can filter the Top 50 table list to only shown tables with a small number of read/write
accesses, but are big in their size.
The example in the above screen shot shows the Top 50 list of tables that have less that 5000
reads and are bigger then 150 MB. The list shows 4 tables. These 4 tables might be
candidates for moving to the SAP HANA Cloud, Data Lake, but that needs to be discussed
with the application and the development team because the way the tables can be accessed
will change when moved to a data lake.
Summary
In this lesson, you have learned to identify which tables have a high memory usage and have a
high read/write load.
LESSON SUMMARY
You should now be able to:
● Use the SAP HANA Cockpit resource monitoring cards
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Use the SAP HANA Cockpit system load monitoring cards
Business Case
As a database administrator, you want to analyze the database sessions connected to identify
which applications or which users are currently generating the workload.
Analyzing the sessions connected to your SAP HANA database helps you identify which
applications or which users are currently connected to your system, as well as what they are
doing in terms of SQL execution.
In the SAP HANA cockpit - Database Overview page, search for the Sessions card (1).
The Sessions card (2) shows an overview of the total and running sessions in your SAP HANA
Cloud database instance.
Clicking on the Sessions card title open the Sessions app which, by default, gives a detailed
breakdown (3) of all session n your SAP HANA Cloud database instance. You can see the
following information:
● Active/inactive sessions and their relation to applications
● Whether a session is blocked and, if so, which session is blocking it
● The number of transactions that are blocked by a blocking session
● Statistics such as average query runtime and the number of DML and DDL statements in a
session
● The operator currently being processed by an active session
Use the filter options to search for specific sessions. You can use the following filter options:
Connection Status:
● Running - A statement is executing.
● Idle - No statements are currently executing on this connection.
● Queuing - The connection is currently queued. The status changes to RUNNING when it is
dequeued (this depends on the system's re
● Empty - A historic connection that is removed after 1 hour.
Hint:
The connection removal time can be configured in indexserver.ini [session]
connection_history_lifetime = 60 # minutes
The Transaction Status column can show the following different states: INACTIVE, ACTIVE,
PRECOMMITTED, ABORTING, PARTIAL_ABORTING, or ACTIVE_PREPARE_COMMIT
depending on the
You can also exclude your own transaction and/or filter on a specific application.
See the following video for selecting a specific session.
Select the session that you want to analyze closer. As soon as you selected the row, the
buttons Navigate to … and Cancel Session … in area (2) become active.
The Save as button (2) allows you to save the data sets as a text, CSV, or HTML file.
The Navigate to … button (2) allows you to navigate from the Session application to the
Threads application or vice versa. From the selected session you can jump directly to the
threads or blocked transactions belonging to that selected session.
The Cancel Sessions button (2) allow you to terminate the selected running session or
operation.
Summary
In this lesson, you have learned how to monitor the database sessions using the Sessions
Card provided in the SAP BTP version of the SAP HANA cockpit.
Use the Threads app to monitor the longest-running threads active in your system. You can
use it to see, for example, how long a thread is running, or if a thread is blocked for a
prolonged period.
Analyzing the threads running in the SAP HANA database can be helpful when analyzing the
current system load.
You can identify which statements or procedures are being executed and at what stage they
are, who else is connected to the system, and if there are any internal processes running as
well. The Threads card provides information about the number of currently active and blocked
threads in the database.
In the SAP HANA cockpit - Database Overview page, search for the Threads card (1).
The Threads card(2) shows an overview of the active and blocked threads in your SAP HANA
Cloud database instance.
Clicking on the Threads card title open the Threads page which, by default, gives a detailed
breakdown (3) of all threads in your SAP HANA Cloud database instance. You can see the
following information:
The Threads page allows you to monitor the longest-running threads in your current system.
You can retrieve more information or customize what is being displayed, for example:
● Filter threads according to Host, Service, Thread Type, Connection Status, Transaction
Status, Owner, or Application.
● Choose the sorting order by checking the Group and Sort box and selecting the sorting
parameters
● See the call stack information on your chosen thread
● Define columns and choose the parameters you want information on
Use the filter options to search for specific threads. You can use the following filter options:
Service - Select threads running on a specific service.
Thread type - More information on thread types, methods and details see SAP Note 2114710 -
FAQ: SAP HANA Threads and Thread Samples
Connection Status:
● Running - A statement is executing.
● Idle - No statements are currently executing on this connection.
● Queuing - The connection is currently queued. The status changes to RUNNING when it is
dequeued (this depends on the system's re
● Empty - A historic connection that is removed after 1 hour.
Select the thread that you want to analyze closer. As soon as you selected the row, the
buttons Navigate to … and Cancel Operations … in area (2) become active.
The Navigate to … button (2) allows you to navigate from the Thread application to the
Sessions application or vice versa. From the selected thread you can jump directly to the
sessions or blocked transactions application belonging to that selected thread.
The Cancel Operations (2) allow you to terminate the selected running thread or operation.
Summary
In this lesson, you have learned how to monitor the database threads using the Threads Card
provided in the SAP BTP version of the SAP HANA cockpit.
Analyzing the current most critical statements running in the SAP HANA database can help
you identify the root cause of poor performance, CPU bottlenecks, or out-of-memory
situations.
In the SAP HANA cockpit - Database Overview page, search for the SQL Statements card (1).
The SQL Statements card (2) shows an overview of the active SQL Statements in your SAP
HANA Cloud database instance.
Clicking on the SQL Statements card title open the SQL Statements page which, by default,
gives an overview and analysis of the most critical statements running in the database.
Using the SQL Statement (1) search field, you can quickly look up a specific SQL statement.
On the SQL Statements page there are four views (2) available:
● Overview - An overview and analysis of the most critical statements running in the
database.
● Active Statements - A list of all statements currently running in the system.
● SQL Plan Cache - Insights into the workload of the SAP HANA database through a list of all
statements currently cached in the SAP HANA database
● Expensive Statement Trace - Analysis of individual SQL queries whose execution time is
above a configured threshold.
Using the Settings button, you can add and remove columns from the display. Which columns
are needed depends on the situation you are investigating. Adjust the displayed columns
according to your needs.
For a detailed investigation press the More (1) button to see the full SQL statement. You can
copy the SQL statement for further analysis or documentation purposes.
You can manage workload in SAP HANA by creating workload classes and workload class
mappings. Click the _SYS_DEFAULT (2) workload class to create a new workload class to
dynamically manage the resource consumption of the selected query. A workload restriction
can be mapped to a specific schema, object, application or database user, application or user
group.
Summary
In this lesson, you have learned how to use the SQL Statements app provided in the SAP BTP
version of the SAP HANA cockpit.
LESSON SUMMARY
You should now be able to:
● Use the SAP HANA Cockpit system load monitoring cards
Learning Assessment
1. Which tool can be used to perform database administration tasks on SAP HANA Cloud
database instances?
Choose the correct answer.
2. The Alerts card provided in the SAP BTP version of SAP HANA cockpit allows you to
automatically send email messages when database alerts are triggered.
Determine whether this statement is true or false.
X True
X False
4. Which services can you stop or kill in the Manage Services application of SAP HANA
cockpit?
Choose the correct answers.
X A All
X B None
X C Indexserver
X D Compileserver
5. Which SAP HANA cockpit cards start the Performance Monitor app to monitor their KPIs?
Choose the correct answers.
X A Table usage
X B Memory Usage
X C CPU Usage
X D Disk Usage
6. In the Table Usage app, which criteria would identify tables that could be moved to the
SAP HANA Cloud, Data Lake?
Choose the correct answers.
7. Using the Sessions application in SAP HANA cockpit, you can identify the application user
and transaction status of database sessions.
Determine whether this statement is true or false.
X True
X False
8. What can you identify using the Threads app in SAP HANA cockpit?
Choose the correct answers.
X A SQL trace
X B Database trace
X C User trace
Lesson 1
Opening SAP HANA Database Explorer 150
Exercise 15: Open SAP HANA Database Explorer 153
Lesson 2
Examining the SAP HANA Traces 156
Exercise 16: Examine Indexserver Trace 159
Lesson 3
Import Catalog Objects 162
Exercise 17: Import Catalog Objects 165
Lesson 4
Using the Statement Library 168
Exercise 18: Use the Statement Library 171
UNIT OBJECTIVES
● Open the SAP HANA Database Explorer for SAP HANA Cloud databases
● Examine the SAP HANA Traces
● Import Catalog Objects
● Using the Statement Library
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Open the SAP HANA Database Explorer for SAP HANA Cloud databases
Business Case
As a database administrator, you often need to directly work with tables, schemata and so on.
For this the SAP HANA cloud database provides the SAP HANA database explorer.
Navigate from the Trial home page to your dev space (1) where you will find the SAP HANA
Cloud. Click the SAP HANA Cloud (2) button to get an overview of the available SAP HANA
Cloud database instances.
Select the Manage SAP HANA Cloud (3) button to open the SAP HANA Cloud Central. From
there you can start the SAP HANA Cloud, Database Explorer.
Note:
It is also possible to open the SAP HANA database explorer directly from the SAP
HANA Cloud Overview page by selecting the Actions drop-down menu.
To administer your SAP HANA Cloud database instance press the Manage SAP HANA Cloud
(3) button. This will open the SAP HANA Cloud Central where you get a detailed overview of
all the SAP HANA Cloud databases managed by you.
The SAP HANA Cloud Central (1) opens in a new browser tab. This makes it easier to navigate
between the SAP HANA Cloud Central and SAP BTP Cockpit.
Press the °°° (2) button to open the Actions Menu for the selected cloud database. From the
Actions Menu select the Open in SAP HANA database explorer (3) option.
The SAP HANA database explorer - Overview page (1) opens in a new tab and displays a
navigation panel (2) and a SQL Console (3) window.
Note:
In the SAP HANA database explorer, by default, the user DBADMIN is used to
connect to the databases.
In the navigation panel (2) you can add (+ button) or remove databases.
Animation
For more information on this topic please view the animation in the lesson
Opening SAP HANA Database Explorer in your online course.
In a database, you can drill down in the Catalog, Database Diagnostic Files and the HDI
containers.
The catalog represents the data dictionary. In the catalog you will find all Adapter, Indexes,
Libraries, Procedures, data structures, tables, and Schemas.
SAP HANA HDI container consists of a design-time container and a corresponding run-time
container. HDI Containers are used by developers to store and execute their development
work.
Database Diagnosis files include log and trace files, as well as a mixture of other diagnosis,
error, and information files. In the event of problems with the SAP HANA database, you can
check these diagnosis files for errors.
Summary
In this lesson, you have learned how to open and navigate the cloud version of the SAP HANA
database explorer.
LESSON SUMMARY
You should now be able to:
● Open the SAP HANA Database Explorer for SAP HANA Cloud databases
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Examine the SAP HANA Traces
Business Case
As a database administrator, you often need to look at the database trace files to diagnose
and analyze errors. For this the SAP HANA cloud database provides the SAP HANA database
explorer.
The SAP HANA database explorer allows you to diagnose and analyze errors in an SAP HANA
database by viewing the relevant diagnostic files. In the database explorer, the diagnostic files
for online databases are grouped by host, and then by service.
In the SAP HANA database explorer - Overview page, Drill-down in the Database Diagnostic
Files folder until you reach the indexserver folder (1). In the File Browser area all the files from
the indexserver folder are shown.
In the File Browser area, select the indexserver (2) file. The indexserver file will automatically
be opened in a text editor tab in the display area. In the text editor, you can search for error or
warnings by pressing [CTRL]+F.
Right-clicking on a diagnostic file opens the context menu from which you can open, show
files, download, copy the tracefile name or create a shortcut to the trace file.
Summary
In this lesson, you have learned how to find the available database trace files in the SAP HANA
database explorer.
LESSON SUMMARY
You should now be able to:
● Examine the SAP HANA Traces
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Import Catalog Objects
Business Case
As a database administrator, you sometimes need to import tables and data into the SAP
HANA Cloud database. The content import function is provided in the SAP HANA database
explorer.
The SAP HANA database explorer supports you in importing and exporting catalog objects,
including schemas, into your database. The source files must be compressed in .tar.gz
format.
Note:
It is not possible to import binary or CSV objects which have been exported from
the on-premise SAP HANA Platform because the two formats and certain data
types are not compatible.
The SAP HANA database explorer for SAP HANA Cloud supports the following import
sources:
● Local - CSV only
● Amazon S3 - CSV and PARQUET
● Azure Storage - CSV and PARQUET
● Alibaba Cloud OSS - CSV and PARQUET
● Google Cloud Storage - CSV and PARQUET
In the SAP HANA database explorer - Overview page, right click (1) on your SAP HANA Cloud
database to open the context menu.
In the context menu, select the option Import Catalog Objects (2) the Import Catalog Objects
(3) opens is an pop-up window. The Import Catalog Objects function is available on every level
in the databases panel.
In the Import Catalog Objects window specify if you want to import the data from your Local
Computer or from a Cloud Storage Provider (2). After you selected the .tar.gz file from the
storage location press the Import button.
If the import is successful there is a small "Import Completed Successfully" toast (popup
message) in the right top corner. You can also check the existence of the new table in the
schema where you performed the import to. In the above example, I imported the table
Bigtable (3) in the HC200_DEMO schema.
Summary
In this lesson, you have learned how to use the SAP HANA database explorer to import
catalog objects.
LESSON SUMMARY
You should now be able to:
● Import Catalog Objects
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Using the Statement Library
Business Case
As a database administrator, you want to use the SQL statement collection for SAP HANA or
want a location to store your personal monitoring scripts. This is possible using the Statement
Library provided in the SAP HANA database explorer.
Statement Library
During the analysis of complex problems, you might want to determine special database
information that is not entirely available in standard functions. Because of this, SAP provides
a collection of useful SQL statements for SAP HANA database analysis. For information on
how to download the SQL statements, see SAP Note 1969700.
The database explorer statement library comes pre-installed with a set of system-defined
statements that are available in the M_SYSTEM_INFORMATION_STATEMENTS system view
and all statements that are included in the SQL Statement Collection for SAP HANA.
Note:
For the newest SQL statement collection file, see SAP Note 1969700: SQL
statement collection for SAP HANA.
For the SQL statement collection documentation, see SAP Note 1999993: How-
To: Interpreting SAP HANA Mini Check Results.
In the SAP HANA database explorer - Overview page, right click (1) on your SAP HANA Cloud
database to open the context menu.
In the context menu, select the option Show Statement Library (2) the Statement Library (3)
opens is an pop-up window and displays the list of available SQL scripts.
In the Statement Library pop-up window, select the SQL script you want to execute, .e.g.,
Expensive Statement Analysis (1) and the Execute (2) button.
The script will be executed and the results will be shown in a results screen (3) in the display
panel of the screen. To further analyze the results, you can download your results to a flat file
and open the results in an editor tool.
Summary
In this lesson, you have learned how to use the SAP HANA database explorer to use the SQL
scripts available in the Statement Library provided.
LESSON SUMMARY
You should now be able to:
● Using the Statement Library
Learning Assessment
1. When you open the SAP HANA database explorer, it will connect automatically to the
selected database, no additional authentication is required.
Determine whether this statement is true or false.
X True
X False
2. You want to look at the log files of a SAP HANA Cloud database instance, which tool would
you use?
Choose the correct answers.
3. Which file formats are supported by the Import Catalog Objects function in the SAP HANA
database explorer?
Choose the correct answers.
X A CSV
X B JSON
X C Parquet
X D XML
4. The Statement Library in the SAP HANA database explorer allows you to only use the SQL
Statement Collection provided by SAP.
Determine whether this statement is true or false.
X True
X False
Lesson 1
Stopping your SAP HANA Cloud database 179
Exercise 19: Stop a SAP HANA Cloud Database Instance 183
Lesson 2
Starting your SAP HANA Cloud database 186
Exercise 20: Start a SAP HANA Cloud Database Instance 191
Lesson 3
Upgrading your SAP HANA Cloud Database 194
Exercise 21: Check SAP HANA Database Version before Upgrade 199
Exercise 22: Update a SAP HANA Cloud Database Instance (trial) 205
Exercise 23: Check SAP HANA Database Version after Upgrade 209
Lesson 4
Scaling for SAP HANA Cloud 212
Exercise 24: Elastic Scale the SAP HANA Cloud Database Instance 219
Lesson 5
Backing Up an SAP HANA Cloud database 222
Exercise 25: Check for Data and Log Backups 227
Lesson 6
Recovering an SAP HANA Cloud database 230
Exercise 26: Recover Database with Table Check on BigTable 235
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Stop your SAP HANA Cloud database instance
Business Case
As a database administrator, you need to stop your company's SAP HANA Cloud database
deployed in the SAP Business Technology Platform.
Note:
The steps to stop your trial SAP HANA Cloud database instance also apply to a
SAP HANA Cloud database instance that was created in an SAP Business
Technology Platform (BTP) enterprise account.
Your SAP HANA Cloud database instance is part of the SAP Business Technology Platform, to
find your SAP HANA Cloud database instance you need to perform the following steps.
1. Logon to the SAP Business Technology Platform trial account and navigate to the SAP
HANA Cloud database area by following one of these paths:
● For an BTP trial account: <your BTP home page> → <your trial global account> →
<your subaccount> → <your development space> → from the navigation pane select
SAP HANA Cloud button → select the button Manage HANA Cloud
● For an BTP enterprise account: <your BTP home page> → your enterprise global
account> → select the Subaccounts link → <your subaccount> → <your
development space> → from the navigation pane select SAP HANA Cloud button →
select the button Manage HANA Cloud
2. A sign-in tab opens, select your e-mail address to continue the sign in process.
3. In the new tab you are now logged on to the SAP HANA Cloud Central application.
You are now in the SAP HANA Cloud Central application where you get an overview of all the
SAP HANA Cloud database instances that you have deployed in this development space.
The following steps show you how to stop your SAP HANA Cloud database instance:
1. In the SAP HANA Cloud Central application, locate your SAP HANA Cloud database
instance that you want to stop and press the °°° (More) button.
Your SAP HANA Cloud database instance is now being stopped. The whole shutdown process
takes around 30 seconds.
During the writing of this e-learning course I tested stopping on a trial account and on an
enterprise account. On the BTP enterprise account I setup an identical system (30 GB RAM,
120 GB storage and 2 vCPUs) as in the trial account. The stopping time was also around 30
seconds.
Just for fun, and because I could, I created also a system that was a little bit bigger (1 TB RAM,
2760 GB storage and 68 vCPUs). The shutdown time for this empty 1 TB system was also
around 30 seconds.
From these very simple tests nothing can be concluded, but it shows that the trial accounts
have the same or a very similar hardware configuration.
To Stop an SAP HANA Cloud database using the Cloud Foundry CLI execute the following
steps:
Example:
cf update-service HC200-Trial-Database -c '{ "data":
{"serviceStopped": true}}'
Have a look at the Start and Stop an Instance Using the CLI page to have a complete list of
parameters that can be used to stop a database instance.
Summary
In this lesson, you have learned the two different methods how to stop your SAP HANA Cloud
database instance that you previously created in your SAP Business Technology Platform
(BTP) trial account.
LESSON SUMMARY
You should now be able to:
● Stop your SAP HANA Cloud database instance
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Start your SAP HANA Cloud database instance
Business Case
As a database administrator, you need to start your company's SAP HANA Cloud database
deployed in the SAP Business Technology Platform.
Note:
The steps to start your trial SAP HANA Cloud database instance also apply to a
SAP HANA Cloud database instance that was created in an SAP Business
Technology Platform (BTP) enterprise account.
Your SAP HANA Cloud database instance is part of the SAP Business Technology Platform, to
find your SAP HANA Cloud database instance you need to perform the following steps.
1. Logon to the SAP Business Technology Platform trial account and navigate to the SAP
HANA Cloud database area by following on of these paths:
● For an BTP trial account: <your BTP home page> → <your trial global account> →
<your subaccount> → <your development space> → from the navigation pane select
SAP HANA Cloud button → select the button Manage HANA Cloud
● For an BTP enterprise account: <your BTP home page> → your enterprise global
account> → select the Subaccounts link → <your subaccount> → <your
development space> → from the navigation pane select SAP HANA Cloud button →
select the button Manage HANA Cloud
2. A sign-in tab opens, select your e-mail address to continue the sign in process.
3. In the new tab you are now logged on to the SAP HANA Cloud Central application.
You are now in the SAP HANA Cloud Central application where you get an overview of all the
SAP HANA Cloud database instances that you have deployed in this development space.
In your SAP Business Technology Platform trial you can only deploy one SAP HANA Cloud
database instance in the trial subaccount.
Note:
In an SAP Business Technology Platform enterprise account, depending on your
entitlements and remaining quotas, you can deploy multiple SAP HANA Cloud
database instances in a subaccount.
In the SAP Business Technology Platform trial environment your applications and SAP HANA
Cloud database instance are automatically stopped every day at midnight to preserve
resources. This means that you need to start your SAP HANA Cloud database instance every
time when you want to explore and test it's capabilities and features.
Hint:
In an SAP Business Technology Platform enterprise account the applications and
SAP HANA Cloud database instances are NOT stopped at midnight.
The following steps show you how to start your SAP HANA Cloud database instance:
1. In the SAP HANA Cloud Central application, locate your SAP HANA Cloud database
instance that you want to start and press the °°° (More) button.
Your SAP HANA Cloud database instance is now being started. The whole start process takes
around 2.5 minutes.
During the writing of this e-learning course I tested starting on a trial account and on an
enterprise account. On the BTP enterprise account I setup an identical system (30 GB RAM,
120 GB storage and 2 vCPUs) as in the trial account. The starting time was also around 2.5
minutes.
Just for fun, and because I could, I created also a system that was a little bit bigger (1 TB RAM,
2760 GB storage and 68 vCPUs). The starting time for this empty 1 TB system was also
around 2.5 minutes.
From these simple tests nothing can be concluded, but it shows that the trial accounts have
the same or a very similar hardware configuration.
To start an SAP HANA Cloud database using the Cloud Foundry CLI execute the following
steps:
Note:
If you use the SAP HANA Cloud trial account with one organization and space
you can omit the -o, -s and -a options.
Example:
cf update-service HC200-Trial-Database -c '{ "data":
{"serviceStopped": false}}'
Have a look at the Start and Stop an Instance Using the CLI page to have a complete list of
parameters that can be used to start a database instance.
Summary
In this lesson, you have learned the two different methods how to start your SAP HANA Cloud
database instance that you previously created in your SAP Business Technology Platform
(BTP) trial account.
LESSON SUMMARY
You should now be able to:
● Start your SAP HANA Cloud database instance
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Upgrade your SAP HANA Cloud database
Business Case
As a database administrator, you want to upgrade your companies SAP HANA Cloud
database, but before the upgrade you want to check the version of the database to be sure
that everything is prepared.
Your SAP HANA Cloud database instance is part of the SAP Business Technology Platform, to
find your SAP HANA Cloud database instance you need to perform the following steps.
1. Logon to the SAP Business Technology Platform trial account and navigate to the SAP
HANA Cloud database area by following on of these paths:
● For an BTP trial account: <your BTP home page> → <your trial global account> →
<your subaccount> → <your development space> → from the navigation pane select
SAP HANA Cloud button → select the button Manage HANA Cloud
● For an BTP enterprise account: <your BTP home page> → your enterprise global
account> → select the Subaccounts link → <your subaccount> → <your
development space> → from the navigation pane select SAP HANA Cloud button →
select the button Manage HANA Cloud
2. A sign-in tab opens, select your e-mail address to continue the sign in process.
3. In the new tab you are now logged on to the SAP HANA Cloud Central application.
The SAP HANA Cloud Central (1) opens in a new browser tab. This makes it easier to navigate
between the SAP HANA Cloud Central and SAP BTP Cockpit.
Press the °°° (2) button to open the Actions Menu for the selected cloud database. From the
Actions Menu select the Open in SAP HANA cockpit (3) option.
Whenever you start a new SAP HANA Cloud session, you will have to logon to your SAP HANA
Cloud Cockpit. In the Choose Authentication pop-up window, specify you SAP HANA cockpit
user account and password (1). Press OK (2) to logon.
Note:
Your credentials will be remembered until you close your browser session.
If this is your first visit to the SAP HANA cockpit, you might want to change the View display
from Monitoring to All (3) to see all the available SAP HANA cockpit cards.
For quick navigation in the SAP HANA cockpit - Overview page search for Database
Information (1) using the search field.
The Database Information (2) card is found. In the card you can already see the SAP HANA
Version. Select the Database Information if you need more information like SAP HANA
Version History or Installed Plugin version.
Summary
In this lesson, you have learned how to check the version of your SAP HANA Cloud database
instance.
Your SAP HANA Cloud database instance is part of the SAP Business Technology Platform, to
find your SAP HANA Cloud database instance you need to perform the following steps.
1. Logon to the SAP Business Technology Platform trial account and navigate to the SAP
HANA Cloud database area by following on of these paths:
● For an BTP trial account: <your BTP home page> → <your trial global account> →
<your subaccount> → <your development space> → from the navigation pane select
SAP HANA Cloud button → select the button Manage HANA Cloud
● For an BTP enterprise account: <your BTP home page> → your enterprise global
account> → select the Subaccounts link → <your subaccount> → <your
development space> → from the navigation pane select SAP HANA Cloud button →
select the button Manage HANA Cloud
2. A sign-in tab opens, select your e-mail address to continue the sign in process.
3. In the new tab you are now logged on to the SAP HANA Cloud Central application.
In the SAP HANA Cloud Central you see a notification (1) for your database. When you select
the notification, a pop-up window notifies you that a new revision is available.
The upgrade can be started directly from the Upgrade notification (3) or from the °°° (2)
button.
Press the °°° (2) button to open the Actions Menu for the selected cloud database. From the
Actions Menu select the Upgrade (3) option to start the upgrade as well.
As soon as you start the upgrade the system display a information message that the upgrade
involves a restart of your SAP HANA cloud database instance. Confirm this message by
selecting the Yes button.
In the SAP HANA Cloud Central you will see your database Stopping and Starting. This
process is fully automated and after a few minutes the database status is Running again.
In the following video, you will see how to upgrade SAP HANA Cloud to a new version.
Summary
In this lesson, you have learned how to upgrade your SAP HANA Cloud database instance to
the current available version.
Your SAP HANA Cloud database instance is part of the SAP Business Technology Platform, to
find your SAP HANA Cloud database instance you need to perform the following steps.
1. Logon to the SAP Business Technology Platform trial account and navigate to the SAP
HANA Cloud database area by following on of these paths:
● For an BTP trial account: <your BTP home page> → <your trial global account> →
<your subaccount> → <your development space> → from the navigation pane select
SAP HANA Cloud button → select the button Manage HANA Cloud
● For an BTP enterprise account: <your BTP home page> → your enterprise global
account> → select the Subaccounts link → <your subaccount> → <your
development space> → from the navigation pane select SAP HANA Cloud button →
select the button Manage HANA Cloud
2. A sign-in tab opens, select your e-mail address to continue the sign in process.
3. In the new tab you are now logged on to the SAP HANA Cloud Central application.
The SAP HANA Cloud Central (1) opens in a new browser tab. This makes it easier to navigate
between the SAP HANA Cloud Central and SAP BTP Cockpit.
Press the °°° (2) button to open the Actions Menu for the selected cloud database. From the
Actions Menu select the Open in SAP HANA cockpit (3) option.
For quick navigation in the SAP HANA cockpit - Overview page search for Database
Information (1) using the search field.
The Database Information (2) card is found. In the card you can already see the SAP HANA
Version. Select the Database Information if you need more information like SAP HANA
Version History or Installed Plugin version.
LESSON SUMMARY
You should now be able to:
● Upgrade your SAP HANA Cloud database
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Scale an SAP HANA Cloud instance
Business Case
After starting with an initial SAP HANA Cloud instance, your data set and workload is growing
with time. As a responsible administrator, you can scale the resources and change the
memory size and storage size of an SAP HANA Cloud database instance using the SAP HANA
Cloud Central.
Customization is difficult from the fixed scale perspective which you know from an on-
premises SAP HANA instance with a fixed system size, based on records and based on
workload.
The peak workload determines the size of the instance, which usually leads to the need for
oversized hardware to cover peak workloads, which in turn leads to increased costs.
Elastic Scale: The scalability in SAP HANA Cloud is elastic. With SAP HANA Cloud you follow
actively a customer based resource management path. As you have learned in the previous
lessons, you start provision with an initial SAP HANA Cloud instance size and then grow with
your data and workload OR you shrink with your workload. This means that you monitor your
workload and edit the related resources to your needs to get a pay-as-you-go consumption
based pricing approach.
Characteristics of SAP HANA Cloud - Elastic Scale:
● Dynamic resource management- Elastic compute and storage resources for specific
projects.
● No upfront costs- No fixed hardware costs, but a really pay-what-you-use approach.
● No oversized or undersized system- React quickly to new and/or changed workloads.
Note:
Self-service scaling is only possible for an SAP BTP enterprise account.
Talking about dimensional scaling in SAP HANA Cloud, you can see the dimensions of
scalability, based on data set requirements or computation requirements. There are two
dimensions to consider (not entirely independent): One is the Compute dimension and the
other is the Storage dimension. Starting with a single-node instance that you can scale up,
means you can add compute power or you can add memory to your single node SAP HANA
Cloud instance. The instance does not adjust itself dynamically or automatically on demand,
but flexibility supports the elastic scaling approach.
As a user with the role SPACE DEVELOPER you can change and edit the memory size and
storage size of an SAP HANA Cloud database instance using the SAP HANA Cloud Central.
After provisioning, it can only be scaled up. Increasing the memory size of the instance can be
achieved as a self-service approach, while down-scaling is possible through a support service
request. The disk storage space is automatically allocated according to the size of memory of
your instance.
Working actively in the Edit Configuration screen provides the following system behavior:
● Scaling up the memory, also increases the number of vCPUs (compute) and disk (storage)
values.
● Scaling down the memory only reduces the number of vCPUs (compute), not the disk
(storage) space.
● Scaling up and down the disk (storage) space, neither the memory nor the number of
vCPUs (compute) is changed.
After you have set your required values and clicked the Save button, the configuration
changes will be carried out immediately and your SAP HANA Cloud database instance will
restart.
Caution:
After provisioning, your SAP HANA Cloud database instance can only be scaled
up. If you want to decrease the memory size of the instance, please submit a
service request. If you are consider requesting a memory downsizing, also
consider how you will handle the disk storage size as well.
Animation
For more information on this topic please view the animation in the lesson
Scaling for SAP HANA Cloud in your online course.
The SAP HANA Cloud database instance step sizes are described as in the following overview:
Note:
SAP HANA Cloud Trial instances have a fixed storage size and storage type.
To scale-up an SAP HANA Cloud database using the Cloud Foundry CLI execute the following
steps:
Example:
cf update-service HC200-Trial-Database -c
'{"data":
{
"memory": 64,
"vcpu": 4,
"storage": 200
}
}'
The above command will scale-up the database to 64GB memory, 4 vCPUs and 200GB
storage.
Note:
Using the CLI, you can only increase the memory size of an SAP HANA database
instance. If you want to decrease the memory size of the instance, please submit
a service request. For more information, see Service Requests.
Have a look at the Change the Size of an SAP HANA Database Instance Using the CLI page to
have a complete list of parameters that can be used to scale-up a database instance.
Animation
For more information on this topic please view the animation in the lesson
Scaling for SAP HANA Cloud in your online course.
Summary
In this lesson, you have learned the concept of elastic scaling and how to change the size in an
SAP HANA Cloud, SAP HANA database instance by tailoring compute and storage resources
to evolving needs.
LESSON SUMMARY
You should now be able to:
● Scale an SAP HANA Cloud instance
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Backup an SAP HANA Cloud database
Business Case
You are responsible for an SAP HANA Cloud database instance. In the case of an emergency,
it's your job to recover the SAP HANA Cloud database. That's why you want to make sure that
backups made by SAP are all successful.
Database Backup
SAP employs backup processes and other measures that ensure rapid recovery of business-
critical systems as and when necessary.
SAP HANA offers comprehensive functionality to safeguard your database and ensure that it
can be recovered speedily and with maximum business continuity. The SAP HANA database
instances are continually backed up to safeguard your company data and to ensure that it can
be recovered speedily. The Recovery Point Objective (RPO) is no more than 15 minutes.
Note:
The Recovery Point Objective (RPO is the maximum permissible amount of time
during which operational data may be lost without the ability to recover. It is the
time between the last data or log backup and the disaster.
The backups are encrypted using the capabilities of the infrastructure as a service (IaaS)
provider. To ensure even a higher safety level, the backups are replicated in additional
availability zones in the same region.
Backup Cycle
To ensure data security, it is necessary to perform data and log backups at appropriate
intervals. In the SAP HANA Cloud, SAP HANA database the backups are performed by SAP.
The following backup actions are performed:
● Initial data Snapshot and complete data backup on instance creation
● A complete data backups every 24 hours.
● Automatic log backups every 15 minutes
● Automatic catalog backups every 15 minutes
The daily backups are only created when the database is online. Up to 15 daily backups are
retained, this creates 15 backup generations.
Note:
A backup generation includes all the backup types that were created after a
complete data backup up to the time of the next complete data backup.
Backups in the cloud are managed by SAP. Your database is backed up automatically to
ensure that it can be recovered to its most recent consistent state. It is not possible to make
changes to the backup configuration.
To display more information about database backups you need to open SAP HANA cockpit.
On the Database Overview page, with the All view selected, search for, and then click the
Database Backups card.
The following information from the backup catalog is displayed:
● Time range that the backup catalog covers
● Space occupied by each backup type
● Total size of the backup catalog
● Information about the most recent backups within the selected time range.
By default, the last four weeks are displayed.
Click on a particular backup row to display more details about the backup. In the backup
details, you can see the file name and duration of the backup, it size, the service, and the host
on which it was created.
You can specify what information is displayed or change the order in which the columns are
displayed. Choose Settings. Select what information to display or use the arrow buttons to
change the order. In the same way, you can also customize the backup details pages for each
database.
To recover a SAP HANA database to a certain Point in Time (PIT), you need the most current
Complete Data Backup before the PIT as a starting point. To reach the specified PIT, you need
all the consecutive incremental, differential and log backups.
The Backup Generations view shows an overview from all complete data backups and its
consecutive incremental, differential and log backups grouped together. This view is very
useful to determine the correct recovery start point.
To display the backup generations overview page, choose the chart icon. The chart shows the
start time of every backup generation, it's total size, and the sizes of the full data backup and
the associated delta backups and log backups that can be used in for a recovery.
To customize the information displayed in the backup catalog, choose the Filter icon. In the
dialog, you can filter the following information:
● Backup Type - select the backup types to display.
● Status - select the backup status to display.
● Start Time - Select the time range in which to display the backup generations.
Summary
In this lesson you learned how SAP automatically backups your SAP HANA database instance
in a backup cycle of 15 days. You now also have the knowledge how to verify the success of
the daily backups and how to view all the available backup generations.
LESSON SUMMARY
You should now be able to:
● Backup an SAP HANA Cloud database
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Recover an SAP HANA Cloud database instance
Business Case
You have discovered that during the daily data import cycle on September 21, 2021 at
09:33:08 AM the wrong import file was used. This logical problem needs to be corrected by a
database recovery one second before the import started.
Database Recovery
Animation
For more information on this topic please view the animation in the lesson
Recovering an SAP HANA Cloud database in your online course.
There are many reasons to recover a database. The following, not exhaustive, list gives the
most common reasons.
● Infrastructure failure - Even the cloud consists of hardware and software, such as servers,
network components, storage, visualization software, operating systems and
management tools and they can fail. It is up to the cloud provider to setup safeguards and
redundancies to make sure the failures have minimal to zero impact on the applications
running in the cloud.
● Logical error - are often created by a fault in an application, or report, or a mistake of a
database user.
● Database reset - are often used to rollback the database to a known state after a testing
scenario. This way you can re-run a test several times from the beginning and tryout
different configuration settings..
When a database error has occurred, you can recover an SAP HANA database to a Point in
Time just before the database error occurred. This will fix the problem, but maybe not the root
cause. A best practice should be to first investigate the root cause before you start the
database recovery.
Before the start of the recovery process, you should determine the following:
● Check the backup logs - Use SAP HANA cockpit to displaying the detailed information of
the available backup generations. Having one ore more backup generations available
before the error occurred is a prerequisite to be able to start the recovery process.
● Check the database logs - Check the database log to see if you can pinpoint the cause of
the problem. This will give the exact moment in time when the problem first occurred. Use
this time stamp to set a Point In Time (PIT) for the database recovery. You should also try
to implement a fix to make sure the problem is resolved.
● Talk to the people involved - Talking to the people who were working on the system around
the time the error occurred can give you great insight on what were the steps that lead to
the error. You determine a Point In Time (PIT) and which actions are the possible root
cause from this information.
There are two database recovery options for the SAP HANA Cloud database instance:
● Start Recovery allows you to recover the database instance up to a selected point in time
in the past for which a backup is available. This 'point in time' recovery option does not
apply to instances where SAP HANA Cloud, data lake is attached. Recovery for data lake
instances can only be done through a service request. The database instance will be offline
during the recovery.
● Recreate Instance allows you to fully recover the database instance from the latest
backup. The database instance will be offline during the recovery.
Caution:
You can recreate an instance at any time, but because there is a risk of losing
up to fifteen minutes of data this is normally only done on the advice of the
Support team when no other options are available.
Summary
You now have learned for which reasons you might want to perform a database recovery and
which tasks you need to be perform before starting the recovery process to resolve a error in
an SAP HANA database instance.
LESSON SUMMARY
You should now be able to:
● Recover an SAP HANA Cloud database instance
Learning Assessment
1. You can't stop your trial SAP HANA Cloud database instance, because it's automatically
stopped every night around midnight.
Determine whether this statement is true or false.
X True
X False
2. Which tool can you use to start a SAP HANA Cloud database?
Choose the correct answers.
X D SQL Console
3. Which tool(s) can you use to upgrade your SAP HANA Cloud database instance?
Choose the correct answers.
X C Resident hdblcmgui
X D Resident hdblcmweb
4. How can you scale-up your SAP HANA Cloud, SAP HANA database instance?
Choose the correct answer.
5. How many backup generations are kept for an SAP HANA Cloud, SAP HANA database?
Choose the correct answer.
X A 14
X B 28
X C 15
X D 30
6. From which backup storage location can you recover an SAP HANA Cloud database?
Choose the correct answer.
Lesson 1
Introducing SAP HANA User Management 243
Lesson 2
Creating SAP HANA Cloud Users 247
Exercise 27: Create SAP HANA Cloud User Group 253
Exercise 28: Create User in SAP HANA Cloud 255
Exercise 29: Assign User to Group 257
Lesson 3
Creating SAP HANA Cloud Roles 260
Exercise 30: Create SAP HANA Role 265
Exercise 31: Add Privileges to Role 267
Exercise 32: Assign Role to User 269
Lesson 4
Auditing in SAP HANA Cloud 272
Exercise 33: Auditing SAP HANA Cloud 277
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Understand the SAP HANA Cloud database user concept
Business Case
As a database administrator, you want to understand the SAP HANA Cloud user management
concept.
Database users are created with either the CREATE USER or CREATE RESTRICTED USER
statement, or using the SAP HANA cockpit.
When database users that correspond to real people leave the organization, the user
administrator must intervene to delete these users from the database. When a database user
is deleted, this means that any database objects that were owned by that user are also
automatically dropped, and any privileges granted by that user are automatically revoked.
Standard Users
Standard users correspond to users created with the CREATE USER statement. By default
they can create objects in their own schema and read data in system views. Read access to
system views is granted by the PUBLIC role, which is granted to every standard user.
Restricted Users
Restricted users, which are created with the CREATE RESTRICTED USER statement, initially
have no privileges. Restricted users are intended for provisioning users who access SAP
HANA through client applications and who are not intended to have full SQL access via an
SQL console. If the privileges required to use the application are encapsulated within an
application-specific role, then it is necessary to grant the user only this role. In this way, it can
be ensured that users have only those privileges that are essential to their work.
Compared to standard database users, restricted users are initially limited in the following
ways:
● They cannot create objects in the database as they are not authorized to create objects in
their own database schema.
● They cannot view any data in the database as they are not granted the standard PUBLIC
role.
● They are only able to connect to the database using HTTP/HTTPS.
For restricted users to connect via ODBC or JDBC, access for client connections must be
enabled by executing the SQL statement ALTER USER <user_name> ENABLE CLIENT
CONNECT or enabling the corresponding option for the user in the SAP HANA cockpit.
All the privileges granted to a user, either directly or indirectly through roles, are combined.
This means that whenever a user tries to access an object, the system performs an
authorization check on the user, the user's roles, and directly granted privileges.
Privileges can be granted directly to users of the SAP HANA database. However, roles are the
standard mechanism of granting privileges as they allow you to implement complex, reusable
authorization concepts that can be modeled on business roles.
It is not possible to explicitly deny privileges. This means that the system does not need to
check all the user's privileges. As soon as all requested privileges have been found, the
system skips further checks and grants access.
Standard database users by default have the following features:
● They are authorized to create objects in their own database schema.
● They have the PUBLIC role that contains privileges for filtered read-only access to the
system views. Only objects for which the users have access rights are visible. By default,
this role is granted to every user, except restricted users.
● They have access to the database over ODBC or JDBC and are able to connect to the
database using HTTP/HTTPS.
Summary
In this lesson, you have learned about the SAP HANA Cloud user management concept.
LESSON SUMMARY
You should now be able to:
● Understand the SAP HANA Cloud database user concept
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create SAP HANA Cloud Users
Business Case
As a database administrator, you want to create SAP HANA Cloud user accounts and groups
to easily manage them.
User groups support a separation of user management tasks, allowing you to manage related
users together. User groups are an efficient way to manage users. User groups can have:
● One or more dedicated group administrators
Every user group has at least one dedicated group administrator. This makes it possible to
delegate user management tasks to several users independently of each other. Only the
designated group administrator(s) can manage the users in the group. This could be
useful, for example, to protect highly-privileged users or technical users from accidental
deletion or manipulation.
● A group-specific configuration, such as password policy settings or client connect
restrictions.
Caution:
User groups do not control data access. A user's authorizations (roles and
privileges) control data access.
Hint:
A user can belong to only one user group.
Note:
The password policy of a new user group is by default the password policy of the
database.
If a group-specific value is not explicitly set for a parameter, the value configured in the
password policy of the database appears as the user group value in
USERGROUP_PARAMETERS.
Every user who wants to work with the SAP HANA database must have a database user.
Animation
For more information on this topic please view the animation in the lesson
Creating SAP HANA Cloud Users in your online course.
In the SAP HANA cockpit, you can create and manage standard database users and restricted
database users.
Standard users correspond to users created with the CREATE USER statement. By default
they can create objects in their own schema and read data in system views. Read access to
system views is granted by the PUBLIC role, which is granted to every standard user.
Restricted users, which are created with the CREATE RESTRICTED USER statement,
initially have no privileges. Restricted users are intended for provisioning users who access
SAP HANA through client applications and who are not intended to have full SQL access via
an SQL console. If the privileges required to use the application are encapsulated within an
application-specific role, then it is necessary to grant the user only this role. In this way, it can
be ensured that users have only those privileges that are essential to their work. By default,
restricted users can only connect to the database using HTTP or HTTPS protocols.
Predefined Database Users
In the SAP HANA database there are several predefined (or internal) database users, such as
SYSTEM, SYS, _SYS_STATISTICS and so on.
The most powerful database user, called SYSTEM is reserved for use by SAP. The
corresponding customer administration user is called DBADMIN. This user is not intended for
routine use and after using it to create other administration users, we recommend disabling it.
Animation
For more information on this topic please view the animation in the lesson
Creating SAP HANA Cloud Users in your online course.
When creating a user in SAP HANA Cloud you need to specify how the user can be
authenticated. The following authentication methods are available.
● User name and password (Local or LDAP)
The user can be authenticated by a password stored locally in the SAP HANA database or
remotely in a directory server.
● SAML
The SAML identity provider must already exist and you must be authorized to assign it.
● X.509
X.509 certificate makes use of a Public Key Infrastructure (PKI) to securely authenticate
users. After users receive their X.509 certificates from a certificate issuing Certification
Authority (CA), they can use them to securely access SAP HANA.
● JWT (JSON Web Token)
The JWT identity provider must already exist and you must be authorized to assign it.
To create the user press the save button. The user is created and appears in the list of users
on the left. A new schema is created for the user in the catalog. It has the same name as the
user.
Summary
In this lesson, you have learned about creating SAP HANA Cloud users and groups.
LESSON SUMMARY
You should now be able to:
● Create SAP HANA Cloud Users
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create SAP HANA Cloud roles
Business Case
As a database administrator, you want to create SAP HANA Cloud roles and assign them to
SAP HANA Cloud database user accounts.
To perform operations in the SAP HANA database, a database user must have the necessary
privileges. Users must have both the privilege(s) to perform the operation and to access the
resources (such as schemas and tables) to which the operation applies. Privileges can be
granted to database users either directly, or indirectly through roles that they have been
granted. In this case, the privileges are inherited. Roles are the standard mechanism of
granting privileges to users.
Animation
For more information on this topic please view the animation in the lesson
Creating SAP HANA Cloud Roles in your online course.
Database Roles
A database role is a collection of privileges that can be assigned to either a database user or
another role in runtime. You can create and assign roles in the SAP HANA cockpit.
A role typically contains the privileges required for a particular function or task, for example:
● Business end users reading reports using client tools such as Microsoft Excel
● Modelers creating models and reports
● Database administrators operating and maintaining the database and its users
Privileges can be granted directly to users of the SAP HANA database. However, roles are the
standard mechanism of granting privileges as they allow you to implement complex, reusable
authorization concepts that can be modeled on business roles.
Roles in the SAP HANA database can exist as runtime objects only (catalog roles), or as
design-time objects that become catalog objects on deployment (database artifact with file
suffix .hdbrole).
Catalog Roles
You can create catalog roles in the SAP HANA system using the SAP HANA cockpit. A role
administrator creates the role in the runtime of the SAP HANA system. The database user
grants catalog roles directly, and they can only be revoked by the same user.
You can create a new role directly in runtime and grant it the privileges and roles necessary
for the task or function that it represents on the Role page of the SAP HANA cockpit.
The Runtime (Catalog) roles have the following properties:
● Roles cannot be transported between systems.
Design-Time Roles
Design-time roles can be created using the SAP Web IDE Full-Stack for example, and
deployed using SAP HANA deployment infrastructure (SAP HANA DI, or HDI).
Due to the container-based model of HDI where each container corresponds to a database
schema, HDI roles, once deployed, are schema-specific. An HDI container can be seen as a
database schema and there can be multiple HDI containers within the SAP HANA database.
All database objects deployed within the container are owned by container-specific technical
object owners.
The Design-Time roles have the following properties:
● Roles can be transported between systems.
● Roles are developed as design-time objects within a project stored in a repository.
● Roles are owned by the object owner of the container.
● Any container or container group administrator with the EXECUTE privilege on these
procedures can grant and revoke roles. ny user with the system privilege ROLE ADMIN can
also grant and revoke roles.
Summary
In this lesson, you have learned about creating SAP HANA Cloud roles and assign them to
database users.
LESSON SUMMARY
You should now be able to:
● Create SAP HANA Cloud roles
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Setup auditing for the SAP HANA Cloud, SAP HANA database
Business Case
The security team has informed you that your SAP HANA Cloud was screened, and it was
found that no auditing was activated. The security team asked you to setup the
recommended SAP HANA Cloud Basic policies and an additional that logs all database
connections to the SAP HANA Cloud database instance.
The auditing feature of the SAP HANA Cloud, SAP HANA database allows you to monitor and
record selected actions that are performed in your database. To use this feature, first activate
auditing for your database instance. Next you create and activate the audit policies that are
required. After activating an audit policy the audit trail will provide you with information on
who did what and when in the database.
This allows you, for example, to log and monitor read access to sensitive data or who
unsuccessfully tried to log-on to the database. The following database actions are typically
audited:
● Access to or changing of sensitive information
● Creation or deletion of database objects
● Authentication of users
● Changes to user authorization
● Changes to system configuration
An audit policy defines the actions that are to be audited. It also outlines the conditions under
which the action must occur for it to be relevant for auditing. When an action occurs, the
policy is triggered and an audit event is written to the audit trail. Audit policies are specific to
each database.
Audit logging is disabled by default. You can use the SAP HANA cockpit or SQL to enable
auditing, configure audit trail targets, and create audit policies.
Note:
The actions that are audited are limited to those that take place inside the
database engine while it is running. Therefore, database restart and recovery will
not be audited.
If auditing is active, certain actions are always audited and are therefore not available for
inclusion in user-defined audit policies. In the audit trail, these actions are labeled with the
internal audit policy name MandatoryAuditPolicy. Mandatory audit actions include the
following:
● Creation, modification, or deletion of audit policies
● Enabling or disabling audit policies
● Deletion of audit entries from the audit trail
Although auditing does not directly increase the security of your database, a well designed
audit can help you achieve greater security in the following ways:
● Detect security vulnerabilities if too many privileges were granted to certain users
● Reveal attempts to breach security
● Protect the system owner against accusations of security violations and data misuse
● Allow the system owner to meet security standards
Auditing provides better visibility on what actions were performed or attempted in the SAP
HANA database. It is therefore recommended to create a basic set of policies.
Note:
For a quick start, SAP HANA cockpit provides a Auditing Basic Setup wizard to
help you apply SAP's recommended auditing policies settings.
In general, customers create audit policies for monitoring and recording activity in their
database with an audit log that writes to a local database table. Use the SAP HANA cockpit or
the SQL Console in SAP HANA database explorer to create and activate audit policies, read
the audit trails.
Note:
SAP uses auditing to monitor certain critical security events in customer systems,
but does not have visibility on any business data.
To create and activate an audit policy In the SQL Console you can use the following
commands:
-- The SQL statement shown here creates the same audit policy as the
demonstration shown in SAP HANA cockpit.
For each occurrence of an audited action, one or more audit entries are created and written to
the audit trail.
Audit entries are accessible through the public system view AUDIT_LOG, as well as the union
of these views ALL_AUDIT_LOG. The table below describes the layout of the full audit trail,
that is ALL_AUDIT_LOG.
Note:
Only SELECT operations can be performed on these views by users with the
system privilege AUDIT OPERATOR, AUDIT READ, or AUDIT ADMIN. AUDIT READ
also allows access to the AUDIT LOG table.
Summary
In this lesson, you have learned what auditing in SAP HANA cloud is, and how to perform the
Auditing Basic Setup. You created an auditing policy for a SAP HANA Database instance and
checked the resulting auditing trail.
LESSON SUMMARY
You should now be able to:
● Setup auditing for the SAP HANA Cloud, SAP HANA database
Learning Assessment
X A Standard user
X B Privileged user
X C Super user
X D Restricted user
X A Kerberos
X C SAML
X D JWT
3. Which privileges types are available in the SAP HANA Cloud authorisation concept?
Choose the correct answers.
X A Application privileges
X B System privileges
X C Analytical privileges
X D Package privileges
4. What events can you audit with an audit policy from an SAP HANA Cloud, SAP HANA
database?
Choose the correct answers.
X A Table access
X C Backint connections
X D Database recovery