Abstract: 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.

Abstract: A system for an in-memory row storage architecture can be provided. In some implementations, the system performs operations including processing a database statement comprising a first database transaction affecting one or more rows in an in-memory row store, registering the database statement at a start of execution of the database statement, the start of execution occurring at a first time, unregistering the registered database statement at an end of execution of the database statement, determining a second time at which execution of an oldest currently registered database statement was started, assigning a garbage collection thread to a second database transaction committed at a third time and affecting at least one row of the plurality of rows, and activating the garbage collection thread to reclaim memory within the in-memory row store when the third time is less than the second time. Related systems, methods, and articles of manufacture are also described.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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 for a row identifier (ROWID) of a row of a table of a database, wherein the lookup request identifies a row position of the ROWID. A page corresponding to the row position is identified from an address vector stored in memory storage. The identified page is loaded from the disk storage to the memory storage. The row position is identified within the page from the memory storage. The ROWID stored in the row position is identified within the page. The ROWID is returned responsive to the lookup request.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: A system for an in-memory row storage architecture can be provided. In some implementations, the system performs operations comprising determining that data stored at a first location in a persistent page store is active, copying the data to a second location in an in-memory row store in response to determining that the data is active, indexing the data in an index table in response to determining that the data is active, accessing the data at the second location in the in-memory row store based on the index table, and performing an update of the data in the in-memory row store. Related systems, methods, and articles of manufacture are also described.

Abstract: Among the various aspects of the present disclosure is the provision of a hydrogel-based substrate comprising an aldehyde-containing component, such as N-ethanal acrylamide. The hydrogel component allows for functionalization of a hydrogel through conjugation of proteins (e.g., collagen) to the hydrogel in the absence of a post hoc crosslinking component.

Abstract: Disclosed herein are system, method, and computer program product embodiments for synchronizing an unsynchronized distributed database system. An embodiment operates by locking, by a second node, partitions in the second node based on first information received from, a first node responsive to execution of partition utility based on a first query received by the first node. Blocking, by the second node, a second query to a data portion of the partitions in the second node based on the first information. Locking, by the second node, second node object metadata based on second information received from the first node. Receiving, by the second node, changes to first node object metadata and applying the changes to the second node object metadata. Unlocking, by the second node, the partitions in the second node and the second node object metadata while unblocking the second query.

Abstract: Example embodiments of a database employing an efficient form of multi-version concurrency control (MVCC) are described. In an example embodiment, in response to receiving an update command for a first row of a plurality of rows of a database, an image of the first row stored in a first memory area is stored in a second memory area. In a third memory area storing a first database structure and associated pointer corresponding to the image of the first row stored in the first memory area, a second data structure and associated pointer corresponding to the image of the first row in the second memory area are stored. The second data structure is linked to the first data structure. The image of the first row in the first memory area is overwritten with an image of a new version of the first row provided in the update command.

Abstract: A multi-layer data structure is configured to access rows, pages, and locks stored in memory of a database. The multi-layer data structure may include a row mapping table configured to convert a row identifier of a row in the database into a row address of the row to be accessed stored in a cache memory. The row mapping table may be used to compare bits of the row identifier with corresponding bits of the row address in the cache memory. Each layer of multi-layer row mapping table can be configured to store certain of the bits oldie row address and the row address can be determined by comparing the bits of the row address with the corresponding bits of the row identifier at each layer of the data structure.

Abstract: 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.

Abstract: A system for an in-memory row storage architecture can be provided. In some implementations, the system performs operations including processing a database statement comprising a first database transaction affecting one or more rows in an in-memory row store, registering the database statement at a start of execution of the database statement, the start of execution occurring at a first time, unregistering the registered database statement at an end of execution of the database statement, determining a second time at which execution of an oldest currently registered database statement was started, assigning a garbage collection thread to a second database transaction committed at a third time and affecting at least one row of the plurality of rows, and activating the garbage collection thread to reclaim memory within the in-memory row store when the third time is less than the second time. Related systems, methods, and articles of manufacture are also described.

Abstract: A system for an in-memory row storage architecture can be provided. In some implementations, the system performs operations comprising determining that data stored at a first location in a persistent page store is active, copying the data to a second location in an in-memory row store in response to determining that the data is active, indexing the data in an index table in response to determining that the data is active, accessing the data at the second location in the in-memory row store based on the index table, and performing an update of the data in the in-memory row store. Related systems, methods, and articles of manufacture are also described.

Abstract: A transaction descriptor associated with a vertical chain of row versions is received. The vertical chain of row versions is traversed. The vertical chain is part of a grid structure formed by a number of vertical chains intersected with a number of horizontal chains. A link to a current row version is terminated. A link from the current row version to an older row version in a horizontal chain is locally stored and terminated. The older row version is set as ready for garbage collection. The current row version is set as ready for garbage collection. A link from the current row version to a next row version in the horizontal chain is locally stored and terminated. The next row version is appointed as current.

Abstract: Example embodiments of a database employing an efficient form of multi-version concurrency control (MVCC) are described. In an example embodiment, in response to receiving an update command for a first row of a plurality of rows of a database, an image of the first row stored in a first memory area is stored in a second memory area. In a third memory area storing a first database structure and associated pointer corresponding to the image of the first row stored in the first memory area, a second data structure and associated pointer corresponding to the image of the first row in the second memory area are stored. The second data structure is linked to the first data structure. The image of the first row in the first memory area is overwritten with an image of a new version of the first row provided in the update command.

Abstract: 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.