Abstract: Arrangements for dynamic selection of delta client copy strategies are provided. An intelligent client copy computing platform may determine whether a database table of a source client is empty. If not, the copy computing platform may determine whether the database table has changed. If not, the computing platform may determine whether the database table has been copied from a same source client of a last copy operation. If so, the computing platform may determine whether a record count of the source client is the same as the record count of a target client. If not, the computing platform may apply a delta copy algorithm. The algorithm may select records of the source client, deduct records of the target client from those records, insert records that are in the source but not in the target client, and delete records that are in the target but not in the source client.

Abstract: Arrangements for cross-phase parallelization and optimization are provided. A worklist including metadata associated with executing a plurality of process phases may be stored in a database table. An initial phase of the plurality of process phases may be selected. Using the worklist, a long running task associated with a next phase may be identified, and the long running task may include a predecessor task. Based on determining that a process is available in the initial phase, the available process in the initial phase may be used to execute the predecessor task required for the next phase. A next task in the initial phase may be selected. After executing the predecessor task, the long running task may be executed in parallel with an execution of the next task using a remaining available process in the initial phase. The cross-phase parallelization procedure may be repeated for the next phase.

Abstract: Various examples are directed to systems and methods for enterprise resource planning ERP. A customer environment may execute an ERP software application. A DBMS executing at the first customer environment may store a first basis data table comprising a first plurality of basis data units of a first basis data unit type. The DBMS may receive, from the ERP software application, a basis data request for a basis data unit of the first basis data unit type and determine that the basis data unit that is not stored at the first basis data table. The DBMS may access basis data unit from a basis data service system.

Abstract: Arrangements for an intelligent client copy tool are provided. In a client copy procedure, access to a target client may be locked and all target data associated with the target client may be deleted. A before trigger for execution before a modifying operation on a database table may be defined. The trigger may be executed and, based on the trigger identifying a query associated with the modifying operation, access to the database table may be locked and an insert operation may be executed. Then, the trigger may be deleted. Thereafter, the modifying operation on the target client may be performed and access to the database table unlocked. A database view of the database table, including pointers to the source client, may be generated. Nonstatic data may be copied from the source client to the target client using the insert operation. After the copying, the target client may be unlocked.

Abstract: Systems and methods to copy a plurality of source data records of a source client to a target client include deletion of a first set of target data records of a plurality of target data records associated with the target client, each of the first set associated with a key which is not identical to any key of a plurality of source data records, insertion of a second set of source data records into the plurality of target data records, each of the second set of source data records associated with a key which is not identical to any key of the plurality of target data records, and update of a third set of target data records associated with a key which matches a key of one of the fourth set of source data records and which is different from one of the fourth set of source data records.

Abstract: The present disclosure relates to computer-implemented methods, software, and systems for generating a hierarchy of metadata tables for a database comprising containers including tables. The tables are identified by table names and assigned to containers. A first table is assigned to two containers and may define two table instances of the first table. The hierarchy of metadata tables includes a first metadata table defining mappings between container identifiers, table names, table sections, and unique identifiers for corresponding data within table sections of table instances defined with the table names mapped to the container identifiers. In response to receiving a request to generate a replication of table content, a second metadata table is generated to identify a unique set of table instances from the set of the containers based on evaluating the first metadata table. The unique set of table instances comprises data from the database storage without repetition.

Abstract: Systems and methods to copy a plurality of source data records of a source client to a target client include deletion of a first set of target data records of a plurality of target data records associated with the target client, each of the first set associated with a key which is not identical to any key of a plurality of source data records, insertion of a second set of source data records into the plurality of target data records, each of the second set of source data records associated with a key which is not identical to any key of the plurality of target data records, and update of a third set of target data records associated with a key which matches a key of one of the fourth set of source data records and which is different from one of the fourth set of source data records.

Abstract: The present disclosure relates to computer-implemented methods, software, and systems for managing data replication between different source sections and target sections in response to received copy instructions associated with copy profiles. In response to evaluating statistical metadata identifying whether data records in relation to at least one client are included for a table from a first set of tables, a first subset of tables from the first set of tables is determined. In response to evaluating update metadata defining latest updates of tables from the first subset of tables, a second subset of tables from the first subset of tables is determined that defines tables that include updated data records relevant for copying. The second subset tables are iteratively evaluated to define corresponding operations to be performed for tables at the target section and at the source section in the database in relation to the requested copy operation.

Abstract: The present disclosure relates to computer-implemented methods, software, and systems for generating a hierarchy of metadata tables for a database comprising containers including tables. The tables are identified by table names and assigned to containers. A first table is assigned to two containers and may define two table instances of the first table. The hierarchy of metadata tables includes a first metadata table defining mappings between container identifiers, table names, table sections, and unique identifiers for corresponding data within table sections of table instances defined with the table names mapped to the container identifiers. In response to receiving a request to generate a replication of table content, a second metadata table is generated to identify a unique set of table instances from the set of the containers based on evaluating the first metadata table. The unique set of table instances comprises data from the database storage without repetition.

Abstract: The present disclosure relates to computer-implemented methods, software, and systems for generating a hierarchy of metadata tables for a database comprising containers including tables. The tables are identified by table names and assigned to containers. A first table is assigned to two containers and may define two table instances of the first table. The hierarchy of metadata tables includes a first metadata table defining mappings between container identifiers, table names, table sections, and unique identifiers for corresponding data within table sections of table instances defined with the table names mapped to the container identifiers. In response to receiving a request to generate a replication of table content, a second metadata table is generated to identify a unique set of table instances from the set of the containers based on evaluating the first metadata table. The unique set of table instances comprises data from the database storage without repetition.

Abstract: The present disclosure relates to computer-implemented methods, software, and systems for managing data replication between different source sections and target sections in response to received copy instructions associated with copy profiles. In response to evaluating statistical metadata identifying whether data records in relation to at least one client are included for a table from a first set of tables, a first subset of tables from the first set of tables is determined. In response to evaluating update metadata defining latest updates of tables from the first subset of tables, a second subset of tables from the first subset of tables is determined that defines tables that include updated data records relevant for copying. The second subset tables are iteratively evaluated to define corresponding operations to be performed for tables at the target section and at the source section in the database in relation to the requested copy operation.

Abstract: The present disclosure relates to computer-implemented methods, software, and systems for generating a hierarchy of metadata tables for a database comprising containers including tables. The tables are identified by table names and assigned to containers. A first table is assigned to two containers and may define two table instances of the first table. The hierarchy of metadata tables includes a first metadata table defining mappings between container identifiers, table names, table sections, and unique identifiers for corresponding data within table sections of table instances defined with the table names mapped to the container identifiers. In response to receiving a request to generate a replication of table content, a second metadata table is generated to identify a unique set of table instances from the set of the containers based on evaluating the first metadata table. The unique set of table instances comprises data from the database storage without repetition.