Abstract: An example operation may include one or more of receiving a message from an agent installed at a data replication server, the message comprising a status identifier of a checksum validation of a data replication operation, identifying a latency value associated with the data replication server, determining whether a data loss has occurred based on the status identifier of the checksum validation and the latency value, and in response to a determination that the data loss has occurred, transmitting a notification of the data loss to a computing system associated with the data replication server.

Abstract: A method, computer program product, and computer system are provided. Based on an insert/update/delete (IUD) feature being enabled, and based on receiving an IUD request at a massively parallel processing (MPP) database management system (DBMS) engine, identifying a partition optimized for the IUD request. A partition map is loaded corresponding to a partition optimized for only IUD requests. Based on the IUD request being an insert row operation, a new distribution key is calculated by hash. A new partition map is generated, the insert row operation is executed using the new partition map.

Abstract: A method, computer program product, and computer system are provided. Statistics for each columnar table are extracted from an online analytical processing (OLAP) database catalog. A transaction table map is created from transaction log records of an online transaction processing (OLTP) database. The transaction table map includes a counter of log records in a transaction and a timestamp indicating a longevity of the transaction. Based on the counter or the longevity exceeding a predefined threshold, the transaction is transformed, and sent to the OLAP database where it is replayed.

Abstract: Techniques are described with regard to managing transaction size during a database replication process. An associated computer-implemented method includes identifying each of at least one transaction associated with at least one source database stored in a replication capture memory, identifying at least one potential excessive memory transaction by applying, via at least one machine learning pattern detection model, pattern detection to each of the at least one transaction stored in the replication capture memory, and constructing at least one compact data unit associated with each of the at least one potential excessive memory transaction. The computer-implemented method further includes facilitating compact data unit transmission to a replication apply server system in order to replicate the at least one compact data unit associated with each of the at least one potential excessive memory transaction to at least one target database via a replication apply server application.

Abstract: A database replication using heterogenous encoding is provided. Aspects include obtaining a database and analyzing a data pattern of data in the database. Aspects also include identifying a plurality of candidate encoding formats and evaluating a computing cost for encoding the database for each of the plurality of candidate encoding formats. Aspects further include selecting an encoding format from the plurality of candidate encoding formats based at least in part on the computing cost and storing a backup copy of the database using the encoding format.

Abstract: Techniques are described with regard to managing transaction size during a database replication process. An associated computer-implemented method includes identifying each of at least one transaction associated with at least one source database stored in a replication capture memory, identifying at least one potential excessive memory transaction by applying, via at least one machine learning pattern detection model, pattern detection to each of the at least one transaction stored in the replication capture memory, and constructing at least one compact data unit associated with each of the at least one potential excessive memory transaction. The computer-implemented method further includes facilitating compact data unit transmission to a replication apply server system in order to replicate the at least one compact data unit associated with each of the at least one potential excessive memory transaction to at least one target database via a replication apply server application.

Abstract: Embodiments of the invention are directed to database replication using heterogenous encoding. Aspects include obtaining a database and analyzing a data pattern of data in the database. Aspects also include identifying a plurality of candidate encoding formats and evaluating a computing cost for encoding the database for each of the plurality of candidate encoding formats. Aspects further include selecting an encoding format from the plurality of candidate encoding formats based at least in part on the computing cost and storing a backup copy of the database using the encoding format.

Abstract: A computer-implemented method for managing an index table associated with a data table includes obtaining an index entry associated with a key in the data table. The computer-implemented method further includes determining whether an index page associated with the index entry is in a buffer pool, wherein the buffer pool includes a plurality of index pages loaded from the index table and at least one temp index. The computer-implemented method further includes adding, in response to determining that the index page associated with the index entry is not in the buffer pool, the index entry into the at least one temp index. The computer-implemented method further includes consolidating the at least one temp index into the index table.

Abstract: A computer-implemented method for managing an index table associated with a data table includes obtaining an index entry associated with a key in the data table. The computer-implemented method further includes determining whether an index page associated with the index entry is in a buffer pool, wherein the buffer pool includes a plurality of index pages loaded from the index table and at least one temp index. The computer-implemented method further includes adding, in response to determining that the index page associated with the index entry is not in the buffer pool, the index entry into the at least one temp index. The computer-implemented method further includes consolidating the at least one temp index into the index table.

Abstract: A data-replication system replicates a source database to a target database by first intelligently identifying and prioritizing a set of hot queries that have each in the past been submitted to the source database at a rate exceeding a threshold submission rate. Any previously replicated content contained in a database table accessed by a hot query is copied to a set of memory-resident blocks. The blocks are then updated with incremental changes made to the table's contents since the most-recent previous replication. Each updated block is copied to the target database in order of the priority of the block's corresponding hot query. When all blocks that contain data of a particular table have been copied into the target database, that table becomes available to users of the target database despite the fact that the entire database has not yet been fully replicated.

Abstract: A data-replication system replicates a source database to a target database by first intelligently identifying and prioritizing a set of hot queries that have each in the past been submitted to the source database at a rate exceeding a threshold submission rate. Any previously replicated content contained in a database table accessed by a hot query is copied to a set of memory-resident blocks. The blocks are then updated with incremental changes made to the table's contents since the most-recent previous replication. Each updated block is copied to the target database in order of the priority of the block's corresponding hot query. When all blocks that contain data of a particular table have been copied into the target database, that table becomes available to users of the target database despite the fact that the entire database has not yet been fully replicated.