Sap Se

Eunsang Kim

Juchang Lee

Mihnea Andrei

Joo Yeon Lee

Ivan Schreter

Thorsten Glebe

Yong Sik Kwon

Jaeyoung Choi

Hyunjun Kim

Patrick Voelker

Hanggjun Cho

Sunghoon Lee

Norman May

Jian Luo

Kyungyul Park

Uwe Hahn

Urs Klingsporn

Chang Gyoo Park

Sang Kyun Cha

Kyu Hwan Kim

Jonathan Bregler

Alexander Boehm

Meinolf Block

Lars Dannecker

Werner Thesing

Ivan T Bowman

Jaeyun Noh

Amarnadh Sai Eluri

Frank Renkes

Taehyung Lee

Hyoung Jun Na

Myung Sun Park

Henning Zahn

Andre Schefe

Martin Schindewolf

Ruediger Karl

Rajnish Chitkara

Changgyoo Park

Martin Kittel

Holger Mack

Jaehwa Kim

Juhyeon Jeong

Melanie Handreck

Michael Vander Ploeg

Seoyoon Choi

Abhishek Singhi

Anita Patel

Marlon McKenzie

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 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

Various systems and methods for selective revalidation of data objects are provided. In one example, a computer-implemented method includes updating a target data object of a database system according to a definition statement, and determining whether the definition statement changes one or more object properties of the target data object. In response to determining that the definition statement changes the one or more object properties of the target data object, the method includes revalidating data objects depending on the target data object. In response to determining that the definition statement does not change the one or more object properties of the target data object, the method includes not revalidating the data objects depending on the target data object. In this way, database management performance and speed may be improved while maintaining validity of data objects in a database.

Fine-grained decision on propagation of revalidation

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

Disclosed herein are system, method, and computer program product embodiments for database modification and processing functionality. An embodiment operates by providing a batch of values stored in rows corresponding to a particular column responsive to a request to encrypt the values of the particular column. Encrypted values corresponding the batch of values are received and stored in a hidden column. A status of the rows corresponding to batch of values of the hidden column is updated to indicate in which rows of the hidden column the received encrypted values have been stored. Updated encrypted values are received and stored in the hidden column. The particular column is replaced with the hidden column.

Database modification and processing system

RTR of a database transaction to a replica table may include receiving replication and transaction commit log entries (representing a database transaction). The replication log entry has a row-ID value, and the row at the replica table has a row-ID value. The replication log entry may be dispatched to a parallel log replayer and the associated transaction commit log entry to a transaction commit log replayer. The row-ID values may be compared, and the replication log entry is replayed at the parallel log replayer based on the comparison. The database transaction may then be committed to the replica table by replaying the associated transaction commit log entry at the transaction log replayer, wherein the database transaction is associated with row-level parallel replay having transactional consistency and DDL replication and reconstruction of a DDL statement at the replica system is associated with one or multiple metadata update log entries.

Real-time cross-system database replication for hybrid-cloud elastic scaling and high-performance data virtualization

Systems and methods for generating a metadata log in a database recovery system include generating, at its primary system, a metadata log for a logging period. A change applied to a metadata object accessible from the primary system is detected, and upon detection, the system identifies a pair of a unique metadata identifier and a metadata type for the changed metadata object and determines a metadata structure of the changed metadata object. A data exchange object for the metadata structure is generated and a data exchange element from the data exchange object is created. The metadata log is updated with log information that includes the data exchange element and the pair, which is associated with the data exchange element. Upon the logging period ending, the metadata log is transmitted to a secondary system of the database recovery system for replaying. Related apparatus, systems, techniques and articles are also described.

Logical logging for in-memory metadata store

Systems and methods for generating a platform-independent metadata catalog framework of a database system are disclosed. These include receiving, at the database system, a metadata object, and determining a version of the received metadata object. Responsive to determining that a metadata catalog, which has catalog entries associated with unique versions of metadata objects, does not include a catalog entry associated with the version of the received metadata object, a catalog entry in the metadata catalog is created. The created catalog entry is then associated with the version of the received metadata object. Furthermore, a version number based on the version of the received metadata is generated, which is associated with the created catalog entry. Related apparatus, systems, techniques and articles are also described.

Metadata cataloging framework

Disclosed herein are system, method, and computer program product embodiments for performing garbage collection on a multi-version concurrency control information in the database management system. An embodiment operates by determining, using multi-version concurrency control (MVCC) information, when a row manipulated by a write transaction is visible to a plurality of readers accessing a table that includes the row. The MVCC information for the row includes at least a creation timestamp, a destruction timestamp and a row state. Once the row is visible to the plurality of readers, garbage collecting at least the creation timestamp or the destruction timestamp in the MVCC information. After the creation timestamp or destruction timestamp have been garbage collected, the plurality of readers use the row state to determine accessibility of the row in the table.

Garbage collection of versions driving the garbage collection of multi-version concurrency control timestamps

A plurality of transactions are handled in a database. Each transaction comprises a plurality of operations on at least one record in the database with at least two of the transactions being handled concurrently. Thereafter, a temporary timestamp is assigned to each record that is based, at least in part, on the corresponding transaction. A first transaction among the plurality of transactions is subsequently committed. Afterwards, re-stamping of at least one commit timestamp modified by the first transaction is delegated. Related apparatus, systems, techniques and articles are also described.

Delegation of database post-commit processing

Techniques and solutions are provided for performing transactions within a database system that stores database data using a row store and a column store. For example, a transaction that performs operations to update data in both the row store and the column store can use the same transaction object. The state of the transaction can be atomically changed. For example, the state of the transaction object can be atomically changed from uncommitted to committed (e.g., set to a commit identifier to represent the committed state).

Multi-version concurrency control across row store and column store

Growing community of inventors

Seoul, South Korea

Eunsang Kim