Sap Se

Patrick Voelker

Jaeyoung Choi

Norman May

Mihnea Andrei

Yong Sik Kwon

Tobias Scheuer

Hyunjun Kim

Eunsang Kim

Ruediger Karl

Hyogi Jung

Robin Joy

Thorsten Glebe

Alexander Boehm

Meinolf Block

Martin Schindewolf

Jian Luo

Martin Kittel

Holger Mack

Uwe Hahn

Urs Klingsporn

Juchang Lee

Christian Bensberg

Dirk Thomsen

Jonathan Bregler

Michael Muehle

Martin Heidel

Lars Dannecker

Werner Thesing

Ivan T Bowman

Sascha Zorn

Beomsoo Kim

Frank Renkes

Myung Sun Park

Henning Zahn

Andre Schefe

Christoph Hohner

Johannes Alberti

Johannes Beigel

Fabian Garagnon

Melanie Handreck

Sergej Hardock

Andreas Hartel

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 reception of a request to move a first database tenant from a first database instance to a second database instance, the first database tenant comprising a first tenant object instance associated with a plurality of artifacts of the first database instance, the plurality of artifacts including a tenant-level catalog and data. In response to the request, the tenant-level catalog is exported from the first database instance to a shared storage system, the tenant-level catalog is imported to a second tenant of the second database instance from the shared storage system, the data is exported from the first database instance to the shared storage system, the data is imported to the second tenant of the second database instance from the shared storage system, and the first database tenant is dropped from the first database instance.

Database tenant-level move

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 creation of a first instance of a tenant object in a database instance, association of the first instance of the tenant object with a first plurality of database artifacts including first data associated with the first instance of the tenant object, creation of a second instance of the tenant object in the database instance, association of the second instance of the tenant object with a second plurality of database artifacts including second data associated with the second instance of the tenant object, and reception and response to queries on the first data associated with the first instance of the tenant object and to queries on the second data associated with the second instance of the tenant object.

Native multi-tenancy for database system

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

A database system includes a persistent storage system, a memory storing metadata defining a tenant object and a plurality of database artifacts, a first instance of the tenant object, the first instance associated with a first plurality of the database artifacts including first data associated with the first instance of the tenant object, and a second instance of the tenant object, the second instance associated with a second plurality of the database artifacts including second data associated with the second instance of the tenant object. A processing unit is to execute program code of a database instance to cause the database system to encrypt the first data associated with the first instance of the tenant object using a first public encryption key and store the encrypted first data in the persistent storage system, and encrypt the second data associated with the second instance of the tenant object using a second public encryption key and store the encrypted second data in the persistent storage system.

Native multi-tenant encryption for database system

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

A computer-implemented method for database management is provided. The method comprises: receiving, from a client device , first data to be stored in a database system that comprises first data storage configured to store a data table and a deletion history table; storing the first data in second data storage that is external to the database system and that is in communication with the database system via a network; obtaining a link that enables access, via the network, to the first data stored in the second data storage; storing the link in the data table; and performing a deletion operation of the first data, in response to a request from the client device to delete the first data from the database system, wherein the deletion operation comprises: deleting the link from the data table without deleting the first data from the second data storage; and storing the link in the deletion history table with a timestamp corresponding to a point in time when the link is deleted from the data table.

Computer-implemented method for database management, computer program product and database system

Growing community of inventors

Mannheim, Germany

Patrick Voelker