List of task/activity can perform on System database and tenant database.

 Hi Everyone,

In this blog, we are going to see different activities, which can perform on the System database and tenant database. 

It is important to know which activity we can perform on the system and tenant database, as in critical time it helps to save time.

An SAP HANA system comprises multiple isolated databases and may consist of one host or a cluster of several hosts. An SAP HANA system is identified by a single system ID (SID) and contains one or more tenant databases and one system database.

An SAP HANA system is capable of containing more than one tenant database.

A system always has exactly one system database, used for central system administration, and any number of tenant databases (including zero). An SAP HANA system is identified by a single system ID (SID). Databases are identified by a SID and a database name. From the administration perspective, there is a distinction between tasks performed at the system level and those performed at the database level. Database clients, such as the SAP HANA cockpit, connect to specific databases.

All the databases share the same installation of database system software, the same computing resources, and the same system administration. However, each database is self-contained and fully isolated with its own:

 

1. Set of database users
2. Database catalog
3. Repository
4. Persistence
5. Backups
6. Traces and logs

Although database objects such as schemas, tables, views, procedures, and so on are local to the database, cross-database SELECT queries are possible. This supports cross-application reporting, for example.

Things to Remember About the System Database

1. The system database does not have the same functionality as a tenant database.
2. The system database is not a database with full SQL support.
3. The system database cannot be distributed across multiple hosts, in other words, scale-out is not possible.
4. If you need a full-featured SAP HANA database, you always have to create at least one tenant database.
5. The system database does not support Application Function Libraries (AFL) and SAP liveCache applications.
6. Cross-database access between the system database and a tenant database is not possible. The system database can show monitoring data from tenant databases (views in the schema SYS_DATABASES) but can never show actual content from tenant databases.
7. The system database cannot be copied or moved to another host.
8. SAP HANA options can only run in tenant databases.
9. Tenant-specific configurations cannot be set in the system database. Only global settings are allowed.
10. Features can only be restricted or disabled at a high level for tenant databases.

The system database is created during either installation or conversion from a single-container system to a tenant database system. The system database contains information about the system as a whole, as well as all its tenant databases. It is used for central system administration.

Thanks 

Rupesh Chavan