Sap Se

Sap Ag

Ruediger Karl

Mihnea Andrei

Juchang Lee

Stefan A Baeuerle

Joo Yeon Lee

Seyeong Bae

Norman May

Jaeyoung Choi

Patrick Voelker

Tobias Scheuer

Hyogi Jung

Robin Joy

Yong Sik Kwon

Werner Thesing

Hyunjun Kim

Eunsang Kim

Andre Schefe

Jian Luo

Anne Jacobi

Michael Schmitt

Uwe Hahn

Bertram Vielsack

Knut Thies

Sven Krüppel-Berndt

Urs Klingsporn

Ingo Kober

Systems and methods include reception, at a database instance hosting a plurality of database tenants, of a statement for execution in a first database session associated with a first tenant, determination of first tenant-level resource limits associated with the database session, determination, for one or more resources, of a total amount consumed by the first database session, determination, based on the first tenant-level resource limits and the total amount of the one or more resources consumed by the first database session, of whether the statement can be executed by the database instance in compliance with the first tenant-level resource limits, and execution of the statement if it is determined that the statement can be executed by the database instance in compliance with the first tenant-level resource limits.

Monitoring of resource consumption per tenant

Systems and methods include establishment of a first authenticated database session with a first database user of a database instance hosting a plurality of tenants, determination of a first tenant of the plurality of tenants based on a mapping of the first database user to the first tenant, determination of a first workload class based on the first tenant, and management of resource consumption of the first authenticated database session based on the first workload class.

Mapping of tenant-specific database sessions to workload classes

Systems and methods include reception of an instruction to recover a first database tenant of a first database instance to a first point in time, the first database tenant associated with first database artifacts of the first database instance, and the first database instance including two or more database tenants and, in response to the instruction, creation of a second database instance, selection of backup data of the first database instance based on the first point in time, execution of a recovery of the backup data on the second database instance, export of second database artifacts of the first database tenant from the second database instance to a storage, truncation of the first database artifacts from the first database instance, import of the second database artifacts from the storage to the first database instance, and deletion of the second database instance.

Tenant-level database recovery

Techniques and solutions are described for implementing virtual table schemas. A virtual table schema includes a logical pointer that is used to target a table that includes data and is defined according to the virtual table schema. Values assigned to the logical pointer can be used to target tables at different locations, such as in a federated database system or in a cache of a database management system of a central computing system. When data associated with the virtual table is requested, or prior to receiving the request, the data can be stored in a table in the cache. The logical pointer can be updated to reference the cache. If the cache is full, the table can be removed from the cache, and the logical pointer can be updated to reference a table at the federated database system.

Virtual database tables with updatable logical table pointers

Techniques and solutions are described for implementing virtual table schemas. A virtual table schema includes a logical pointer that is used to target a table that includes data and is defined according to the virtual table schema. Values assigned to the logical pointer can be used to target tables at different locations, such as in-memory storage or in dynamic storage of a database management system. The dynamic storage includes an in-memory buffer cache and persistent storage. The logical pointer can be updated to point to the in-memory storage or the dynamic storage, including based on use statistics. Similarly, a table having data for the virtual table can be transitioned between the in-memory buffer cache and the persistent storage, including based on use statistics for the virtual table. A value for the logical pointer can be updated when the table is transferred between the in-memory buffer cache and the dynamic storage.

Systems and methods include establishment of a first database session with a first database user, determine first session variable values associated with the first database session, the first session variable values including a first tenant value, determine a first workload class based on the first tenant value and on zero or more of the other first session variable values, the first workload class including first parameter values specifying first resource consumption limits, and manage resource consumption of the first database session based on the first parameter values.

Workload classes for tenant-level resource isolation

Implementations of the present disclosure include executing a business application on a server device, the business application executing a service based on a base plurality of inputs, accessing a first service variant based on the service, generating a first plurality of input fields based on the first service variant, the first plurality of input fields corresponding to a first plurality of inputs, the first plurality of inputs being a sub-set of the base plurality of inputs, and executing the service based on the first plurality of inputs that is input using the first plurality of input fields.

Service variants for enterprise services

Growing community of inventors

Albstadt, Germany

Ruediger Karl