Sap Se

Won Wook Hong

Hyeong Seog Kim

Ji Hoon Jang

Joo Yeon Lee

Yong Sik Kwon

Jane Jung Lee

Seyeong Bae

Yu Gao

Junpeng Liu

Zhifeng Xu

Younkyoung Lee

Disclosed techniques and solutions can provide improved snapshot replication. Typically, an initial replica obtained using snapshot replication is periodically updated. However, the update process can unnecessarily consume computing resources if data in a source data object has not changed with respect to data in a replica data object. Disclosed techniques check to determine whether a snapshot replica is out of date before obtaining a new snapshot. The checks can be performed on manual request or on the occurrence of triggers, such as receiving a query that accesses the replica data object or according to a schedule. Information for current and prior versions of the remote data object can be compared to determine whether a replica is out of date, such as digest values of contents of the remote data object or timestamps associated with the remote data object.

Change-aware snapshot replication

The present disclosure provides techniques and solutions for executing requests for database operations involving a remote data source in a system that includes an anchor node and one or more non-anchor nodes. A first request for one or more database operations is received, where at least a first database operation includes a data request for a remote data object. It is determined that the first database operation is not an insert, delete, or update operation, and therefore is assignable to the anchor node or one of the non-anchor nodes. The first database operation is assigned to a non-anchor node for execution. In a particular implementation, for a particular set of requests for a database operation, once an insert, delete, or update operation is received for the remote data object, subsequent operations for the remote data object in the set of requests are assigned to the anchor node for execution.

Flexible routing of database operations accessing remote tables

Restoring a database image of a secondary database system comprises initializing the database image from a recovery image that includes metadata logs and non-metadata logs, of which at least one metadata log includes an undo log of non-committed data that is applied to the initialized database image. A first pagelist and first indexes are then rebuilt based on first data segments of the database image and the corresponding metadata objects. The database image is then updated by replaying the metadata redo log generated from the undo log, the metadata logs, and the non-metadata logs. Then, a second pagelist and second indexes for the database system are rebuilt based on second data segments of the database image and the corresponding non-metadata objects, while each of the first data segments is statically separated from the second data segments in physical memory space. Related apparatus, systems, techniques and articles are also described.

Physio-logical logging for in-memory row-oriented database system

Growing community of inventors

Suwon, South Korea

Won Wook Hong