Sap Se

Sybase, Inc.

Amit Pathak

Paresh Manhar Rathod

Colin Florendo

Sebastian Seifert

Robert Schulze

Swati Sharma

Pushkar Khadilkar

Rahul Mittal

Souvik Pal

Nikhil Jamadagni

Jay Gorakhnath Sudrik

Mihnea Andrei

Reza Sherkat

Janardhan Hungund

Christian Lemke

Aditya Gurajada

Simhachala Sasikanth Gottapu

Dheren Gala

Bernhard Scheirle

Adrian Dragusanu

Deepak Shrivastava

Amit Saonerker

Thomas Peh

Werner Thesing

Prateek Agarwal

Mehul Wagle

Guo Gang Ye

Nilesh Gohad

Aditya Kelkar

Gaurav Kumar Gupta

Padmaja Dhairyasheel Thorat

Mukundakrishnan Parthasarathy

Santhosh T Kumar

Anish Maniyar

Neha Shikha Kachhap

Jagadeesha Kanihal

Kantikumar Kantikumar

Amit Sankhla

Samar Desai

Shrikant Awate

Mitali Yadav

A database system detects a query targeting a first database object stored in a unified persistence format in a persistence store, where a first load unit is specified for loading the first database object into an in-memory store. The database system determines whether to convert the first load unit to a second load unit based on one or more conditions. In response to determining to convert the first load unit to the second load unit for the first database object, the first database object is loaded into the in-memory store according to the second load unit without performing a rewrite of the first database object in the persistence store. In an example, the first load unit is a column-loadable unit and the second load unit is a page-loadable unit.

Load unit conversion with unified persistence

A database system detects an operation to move a first database object from an in-memory store to a persistence store, wherein the first database object is in either a page-loadable or column-loadable format in the in-memory store, and wherein the first database object comprises a plurality of subcomponents. Each subcomponent of the first database object is examined separately from other subcomponents of the plurality of subcomponents. In response to determining that a first subcomponent of the plurality of subcomponents has a datatype and a compression type supported by a unified persistence format, the first subcomponent is stored in a unified persistence format in the persistence store. In response to determining that a second subcomponent of the plurality of subcomponents has either a datatype or a compression type which is not supported by the unified persistence format, the second subcomponent is stored in a serial persistence format in the persistence store.

Unified persistence overall feature

A primary database system loads database objects into a primary in-memory store according to a given format. The primary database captures, in replay logs, the loading of the database objects according to the given format. The primary database sends the replay logs to a secondary database system. In response to receiving a replay log, the secondary database checks the value of a log replay configuration parameter. If the configuration parameter is a first value, the secondary database replays the replay log to load the corresponding database objects into a secondary in-memory store according to a first format. If the configuration parameter is a second value, the secondary database replays the log to load the objects according to a second format, and if the configuration parameter is a third value, the secondary database replays the log to load the objects in a same format which was used by the primary database.

Database load unit for replication log replay

A database system detects a query targeting a first database object stored in a unified persistence format in a persistence store. In response to detecting the query, the database system determines whether to load the first database object in column-loadable format or page-loadable format into an in-memory store. In response to determining to load the first database object in the column-loadable format, the database system determines if a first bit representation of one or more corresponding primitives in the persistence store is compatible with a second bit representation used for storing the primitives in the in-memory store. The database system performs a native copy operation to copy the primitives from the persistence store to the in-memory store if the bit representations are compatible, where the native copy operation involves copying the primitives on a page-by-page basis without decoding and encoding values of the one or more primitives.

Native copy mechanism for in-memory and paged primitive data structures

A system and method including receiving a request to update a timestamp associated with database pages of a database instance logically organized into at least one page set, each of the at least one page set including a plurality of the database pages; updating the timestamp associated with each database page in each respective at least one page set; issuing, in response to updating the timestamp associated with a last database page in each of the at least one page set, a write request to write the plurality of database pages in each of the respective at least one page set to a persistent data store; and writing the plurality of database pages in each of the respective at least one page set to a persistent data store, the plurality of database pages written to the persistent data store having an updated timestamp associated therewith.

Performance enhancement for writing database pages

According to some embodiments, a system, method and non-transitory, computer readable medium are provided comprising a memory storing processor-executable program code; and a processing unit to cause the system to: receive a range of persistent volume disk size values from a cloud service provider; receive a value for an upper bound of a number of persistent volume disks attachable to a virtual machine per the cloud service; determine a number of persistent volume disks based on the upper bound, wherein the number is at least two; generate a plurality of configurations of the determined number of persistent volume disks, wherein a configuration is provided for each persistent volume disk size value, and each configuration divides the persistent volume disk size value between two or more persistent volume disks; and aggregate the generated plurality of configurations in a decision table. Numerous other aspects are provided.

Storage for multi-cloud database as a service

Disclosed herein are system, method, and computer-program product embodiments for generating a paged and in-memory representation of a database object. An embodiment operates by maintaining in-memory and paged form primitives unique to the database object or a substructure thereof in a database such that the in-memory and paged form primitives are capable of providing the in-memory and paged representations of the database objects, respectively. Thereafter, a load configuration for the database object is determined. Based on the load configuration, the in-memory and/or paged representations of the database object are generated using the in-memory form primitive or the paged form primitive unique to the database object, respectively. Subsequently, the in-memory and/or paged representations of the database object are stored in the database.

Hybrid column store providing both paged and memory-resident configurations

Disclosed herein are system, method, and computer program product embodiments for storing an object onto a first or second page. An embodiment operates by receiving the object and determining that the first page has sufficient unused space for storing at least one byte of the object. Thereafter, a data block of the object is created to comprise at least one byte of the object. The data block is then stored on the first page or the second page, and a location of the object's first data block is recorded. Thereafter, a pointer corresponding to the location of the object's first data block for loading the object is provided.

Content agnostic memory pageable storage model

Techniques of implementing partition level operations with concurrent activities are disclosed. A first operation can be performed on a first partition of a table of data. The first partition can be one of a plurality of partitions of the table, where each partition has a plurality of rows. A first partition level lock can be applied to the first partition for a period in which the first operation is being performed on the first partition, thereby preventing any operation other than the first operation from being performed on the first partition during the period the first partition level lock is being applied to the first partition. A second operation can be performed on a second partition of the table at a point in time during which the first operation is being performed on the first partition.

Partition level operation with concurrent activities

System, method, and various embodiments for providing a hybrid data storage and load system are described herein. An embodiment operates by receiving a lookup request comprising a row identifier (ROWID) corresponding to a row of a table of a database. Which of a first set of pages corresponds to a sorted position of the ROWID is identified. The identified page of the first set of pages is loaded from the disk storage to the memory storage. A sorted row position of the ROWID is identified from a memory block of the loaded page from the first set of pages. One of a second set of pages that includes the sorted row position is identified. The identified one of the second set of pages is loaded from the disk storage into memory. The loaded identified one of the second set of pages is searched for the unsorted position of the ROWID.

Hybrid data storage and load system with ROWID lookup

A system for an in-memory row storage architecture can be provided. In some implementations, the system performs operations comprising monitoring access to a plurality of rows in a database partition, a first portion of the plurality of rows stored in a persistent page store and a second portion of the plurality of rows stored in an in-memory row store. The operations can further comprise determining workload parameters based on the monitoring, selecting a location for performing a database operation on the database partition based on the workload parameters, and performing the database operation on the database partition within the selected location (e.g., the persistent page store or the in-memory row store). Related systems, methods, and articles of manufacture are also described.

Information life cycle management of in-memory row storage

Disclosed herein are system, method, and computer program product embodiments for providing paged and compressed storage for column data, while maintaining existing access mechanisms for the data. In order to reduce an in-memory footprint for column data, columns may be stored in pageable format using page chains, and only those pages of the column data needed to resolve a query will be placed in memory, and evicted from memory when no longer needed. In order to further reduce the footprint for these columns, compression can be applied, and the compressed column data stored in the same pageable format using page chains. The compressed data includes a plurality of vectors, each of which is converted into pages and stored on the page chain with the others so that they can be efficiently retrieved during database retrieval operations.

Space efficient vector for columnar data storage

Systems and methods may include execution of a database workload on a plurality of database tables, collection of execution statistics associated with execution of the database workload, determination of an in-memory row storage cache size for multi-version concurrency control based on the collected execution statistics, and configuration of a database system to allocate the in-memory row storage cache size for multi-version concurrency control.

Resource estimation for MVCC-enabled database

Growing community of inventors

Pune, India

Amit Pathak