Sap Se

Sap Ag

Michael Muehle

Juchang Lee

Colin Florendo

Martin Heidel

Jaeyun Noh

Chaitanya Gottipati

Thorsten Glebe

Sang Kyun Cha

Rolando Blanco

Chulwon Lee

Alexander Schroeder

Nirvik Basak

Marco Paskamp

Mihnea Andrei

Chang Gyoo Park

Beomsoo Kim

Reiner Singer

Myung Sun Park

Ivan Schreter

Christian Bensberg

Joo Yeon Lee

Kyu Hwan Kim

Thomas Peh

Werner Thesing

Hyoung Jun Na

Vivek Kandiyanallur

Peter Steinemann

Sarika Iyer

Jörn Schmidt

Dirk Thomsen

Steffen Geissinger

Robert Schulze

Yong Sik Kwon

Reza Sherkat

Wolfgang Stephan

Meinolf Block

Lars Fricke

Sascha Zorn

David Wein

Christoph Roterring

Shiping Chen

Carsten Thiel

Panfeng Zhou

Martin Schindewolf

Patrick Voelker

Yongjae Chuh

Changgyoo Park

Christoph Hohner

Johannes Beigel

Deepak Shrivastava

Martin Kittel

Holger Mack

Stephan Kottler

Fabian Garagnon

Felix Knittel

Timo Hochberger

Johannes Haeussler

Awisha Makwana

Günter Radestock

Mohamed Ali Chriki

Sascha Bastke

Christoph Rottering

Sergej Hardock

Andreas Hartel

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

Disclosed herein are system, method, and computer program product embodiments for converting column loadable data in a database into a page loadable format. When a column oriented in-memory database needs to perform an operation on a table, the affected columns must be loaded fully into memory. In some cases, a database may partition tables, allowing for column fragments corresponding to those partitions to be loaded into memory. These column fragments may exceed available memory, such that it is beneficial to convert the column fragment into a page loadable format. Approaches are discussed herein for performing the conversion without the need to update global metadata during the process, allowing for multiple parallel column fragments to be updated, allowing data manipulation language (DML) operations to continue on the column during the conversion process, and reducing the impact of blocked parallel savepoint operations during the conversion process by chunking the conversion process.

In-place load unit conversion

Technologies are described for facilitating transaction processing within a database environment. A commit protocol provides for the atomic commit or rollback of a transaction that includes an operation that modifies a metadata entity of the database system and one or more other operations that modify metadata entities or data records of the database system. Innovations are provided for detecting and resolving deadlocks that may arise during transaction processing. Innovations are also provided for providing versioning of metadata entities, including invalidating metadata entities cached at a slave node during the commit at a master node of a transaction that creates a new version of the metadata entity.

Atomic processing of compound database transactions that modify a metadata entity

A method, computer program product and system are provided. The method, computer program product and system execute a process for storing an object in an object container that is stored in a persistency of a disk storage. The object container has size criteria whereby objects meeting the size criteria of the object container can be assigned to the object container. The object container can facilitate storing multiple objects to optimize disk storage usage by facilitating the assigning of multiple objects to the same disk storage page.

Large object containers with size criteria for storing mid-sized large objects

A computer implemented method is provided comprising receiving a group of transaction logs from a first database, allocating transaction logs from the group of transaction logs to a first queue and to a second queue, generating an end-of-group transaction log indicative of an end of the group of transaction logs, allocating the end-of-group log to the first queue and the second queue; replaying transaction logs from the first queue including the end-of-group transaction log allocated to the first queue, replaying transaction logs from the second queue including the end-of-group transaction log allocated to the second queue; and changing visibility of one or more transactions in response to replaying the end-of-group transaction log allocated to the first queue and the end-of-group transaction log allocated to the second queue. Related apparatus, systems, techniques and articles are also described.

Delayed snapshot isolation for read service at a database

A computer implemented method for manipulating data comprises receiving log transaction information from a primary database system at a secondary database system and parsing the log transaction information to identify data objects that have been modified on the primary database system. The secondary database system determines whether the data objects are present in main memory on the secondary database system and whether the log transaction corresponds to a data manipulation language (DML) query or a data definition language (DDL) query. If the data objects are not in the main memory and the query is a DML query, they are copied from persistence data volumes to the main memory. The data objects in main memory are modified by replaying the log transactions on the data objects in the main memory. Then, the data objects in the persistence data volumes are modified. Related apparatus, systems, techniques and articles are also described.

Replay of redo log records in persistency or main memory of database systems

Systems, apparatus, techniques, articles, and methods include a unified table container for storing data and metadata in pages organized in one or more page chains. A determination is made as to whether the query includes a data definition statement. In response to determining that the query includes a data definition statement, in-memory runtime data is persisted to a persistent volume that is configured to be accessed by the database system. The in-memory runtime data includes one or more first data fields and one or more second data fields that are different from the one or more first data fields. Furthermore, the unified table container includes a persistent runtime data descriptor that is associated with the one or more first data fields and persists the first one or more first data fields when persisting the in-memory runtime data.

Runtime data persistency for in-memory database systems

Objects across multiple database manipulation language (DML) redo log records are cached, during continuous replay of redo log records on a secondary system, for the same table partition to enable reuse of such cached objects. Later, these cached objects can be reused as they are accessed during the sequential processing of DML redo records for a specific table partition.

Caching DML statement context during asynchronous database system replication

A computer implemented method for updating a secondary database includes receiving transaction log information from a primary database system at a secondary database system. The transaction log information comprises a first marker identifying a beginning of an operation comprising a plurality of sub-operations and a second marker identifying an end of the operation. The transaction log information is sequentially parsed, a first marker is identified, and a lock state is created after replaying the first marker to ensure proper serialization of the plurality of sub-operations. The lock state is terminated after replaying the second marker. Related apparatus, systems, techniques and articles are also described.

Synchronization mechanism for serialized data log replay in database systems

Disclosed herein are system, method, and computer program product embodiments for altering the data type of a column in a database. An embodiment operates by converting an original dictionary associated with a column into a new dictionary. The new dictionary stores the values of the original dictionary using a different data type. An index vector containing the keys of the original dictionary is then updated to contain the associated keys of the new dictionary. Because the size of the original dictionary is often substantially smaller than the number of rows in the associated column, this dictionary conversion decreases the computation cost to the database system of altering the data type of the column and reduces or even minimizes database downtime for users.

Altering data type of a column in a database

A computer implemented method for initializing a secondary database system includes receiving table state information from a primary database system at a secondary database system. The table state information includes information identifying which tables had an open operation during a savepoint event. Metadata associated with the tables is parsed to identify table state information from the metadata and a lock is created for each table identified as having an open operation during the savepoint event. Afterwards, log transaction information is sequentially parsed. Related apparatus, systems, techniques and articles are also described.

Persistence and initialization of synchronization state for serialized data log replay in database systems

Testing a database replication system within a multi-container system architecture comprises receiving a first request for creating a database recovery system within a multi-container system architecture. The multi-container system architecture is configured to contain a plurality of tenant databases and a system database, and the database recovery system includes a primary system and a secondary system. The primary system is then identified from the information in the first request. Upon identification, a first tenant database included in the plurality of tenant databases is determined that corresponds to the identified primary system. Upon determining the first tenant database, a second tenant database of the plurality of tenant database is generated that corresponds to the secondary system, and which is enabled to test replicating information that would otherwise be associated with the first tenant database. Related apparatus, systems, techniques and articles are also described.

Testing database replication with multi-container system architecture

A computer-implemented method, a computer-readable medium and a system are provided. A transaction master for each of a plurality of transactions of a database is provided. Each transaction master is configured to communicate with at least one transaction slave to manage execution of a transaction in the plurality of transactions. Each transaction master configured to perform generating a transaction token to specify data to be visible for a transaction on the database, the transaction token including a transaction identifier for identifying whether the transaction is a committed transaction or an uncommitted transaction, receiving a request to commit the transaction, initiating, based on the request, a two-phase commit operation to commit the transaction. The two-phase commit operation includes preparing for committing the transaction, writing a committed transaction to a memory, optimizing the two-phase commit operation by omitting a phase of the two-phase commit operation, generating an acknowledgement of the committed transaction. The plurality of transactions of the database are executed with each transaction master.

Distributed transaction management using two-phase commit optimization

Growing community of inventors

Walldorf, Germany

Michael Muehle