Abstract: Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives data from a subset of a first set of exchange tables stored in a first database of a source system. The program further creates a second set of exchange tables in a second database of the device. The program also creates a set of shadow tables in the second database of the device. The program further adapts the second set of exchange tables and the set of shadow tables to a higher upgrade version. The program also performs object generation based on the second set of exchange tables and the set of shadow tables. The program further drops the set of shadow tables. The program also receives a set of application tables from the source system. The program further adapts the set of application tables to the higher upgrade version.

Abstract: Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives data from a subset of a first set of exchange tables stored in a first database of a source system. The program further creates a second set of exchange tables in a second database of the device. The program also creates a set of shadow tables in the second database of the device. The program further adapts the second set of exchange tables and the set of shadow tables to a higher upgrade version. The program also performs object generation based on the second set of exchange tables and the set of shadow tables. The program further drops the set of shadow tables. The program also receives a set of application tables from the source system. The program further adapts the set of application tables to the higher upgrade version.

Abstract: Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives data from a subset of a first set of exchange tables stored in a first database of a source system. The program further creates a second set of exchange tables in a second database of the device. The program also creates a set of shadow tables in the second database of the device. The program further adapts the second set of exchange tables and the set of shadow tables to a higher upgrade version. The program also performs object generation based on the second set of exchange tables and the set of shadow tables. The program further drops the set of shadow tables. The program also receives a set of application tables from the source system. The program further adapts the set of application tables to the higher upgrade version.

Abstract: Techniques for predicting the downtime of a software system due to an upgrade of the system are provided. In one set of embodiments, a computer system can receive training data comprising (1) measured downtimes, (2) upgrade object information, (3) upgrade configuration information, and (4) system hardware information for past upgrades of the software system across different operating environments. Using this training data, the computer system can train a machine learning (ML) model to predict (1) based on (2), (3), and (4). The computer system can then receive a query comprising upgrade object information for a future upgrade U, upgrade configuration information for upgrade U, and system hardware information for an operating environment E. Based on these inputs, the computer system can use the ML model to generate a downtime value indicating the predicted downtime that will be experienced by the software system when upgrade U is applied to the system in operating environment E.

Abstract: Techniques for predicting the downtime of a software system due to an upgrade of the system are provided. In one set of embodiments, a computer system can receive training data comprising (1) measured downtimes, (2) upgrade object information, (3) upgrade configuration information, and (4) system hardware information for past upgrades of the software system across different operating environments. Using this training data, the computer system can train a machine learning (ML) model to predict (1) based on (2), (3), and (4). The computer system can then receive a query comprising upgrade object information for a future upgrade U, upgrade configuration information for upgrade U, and system hardware information for an operating environment E. Based on these inputs, the computer system can use the ML model to generate a downtime value indicating the predicted downtime that will be experienced by the software system when upgrade U is applied to the system in operating environment E.

Abstract: Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives data from a subset of a first set of exchange tables stored in a first database of a source system. The program further creates a second set of exchange tables in a second database of the device. The program also creates a set of shadow tables in the second database of the device. The program further adapts the second set of exchange tables and the set of shadow tables to a higher upgrade version. The program also performs object generation based on the second set of exchange tables and the set of shadow tables. The program further drops the set of shadow tables. The program also receives a set of application tables from the source system. The program further adapts the set of application tables to the higher upgrade version.

Abstract: Continuous access to an application and associated data is provided during a modification (for example, an upgrade) of the application. Shared tables are used to perform parallel changes in databases associated with an original database schema, a temporary database schema, and an upgraded database schema. Aliases are used to access shared tables from some database schemas. The use of shared tables obviates a separate merging of data written by different tools and/or systems during an upgrade of the application. Related methods, apparatuses, systems, techniques and articles are also described.

Abstract: The present disclosure describes methods, systems, and computer program products for providing multi-level user interface theming.

Abstract: A database definition language (DDL) description of a database table can be copied to create a temporary copy of the database table as part of a table upgrade to change a structure of the database table to an upgraded structure. The temporary copy of the database table can be renamed, and the DDL description in the temporary copy of the database table can be changed to an intermediate state while a runtime object and a database object of the database table remain in original states. The changed DDL description can be activated in the temporary copy of the database table such that the runtime object and the database object are updated to the intermediate state, and the temporary copy of the database table can be renamed to an original name of the database table, thereby activating the temporary copy as the database table with the upgraded structure.

Abstract: In one general aspect, a computer system can include instructions stored on a non-transitory computer-readable storage medium. The computer system can include a program database module configured to define, at a shadow system, a shadow program database including data and a structure collectively defining an upgrade to an original program database on an original system. The computer system can include a basis module configured to define at the shadow system a shadow basis database related to start functionality of the shadow system. The computer system can also include a downtime execution module configured to trigger the shadow system to change from a downstate to an upstate based on a combination of data included in the shadow basis database and the data of the shadow program database.

Abstract: A temporary system is described to provide, during an upgrade of an application implemented using an original system, a continuous access to the application. A copy of a first data-set characterizing a first version of the application is generated on the temporary system when the upgrade becomes available. A selective access to the copy on the temporary system is enabled while preventing access to the first data-set on an original system. The first data-set on the original system is upgraded to form a second data-set characterizing a second version of the application, and a testing of the second data-set is performed. When a result of the testing indicates that the second data-set should be implemented, an access to the second data-set on the original system is enabled while preventing access to the copy on the temporary system. Related methods, apparatus, systems, techniques and articles are also described.

Abstract: A zero downtime upgrade procedure upgrading a source system to a target system is initiated that prepares software for the target system in parallel to the operation of the source system. As part of the upgrade procedure, source tables of the source system are renamed. Thereafter, the renamed source tables are cloned for the target system. Further, the renamed source tables are equipped with database triggers to transfer data from the renamed source tables to the cloned tables used by the source system according to a source database schema. Next, the target tables are generated that include updated software content for later use by the target system while the source tables are used via a bridge database schema. Tables can then be shared between the source database schema accessed via the bridge database schema and the target system.

Abstract: The subject matter described herein relates to providing a continuous access to a database at times, including when the database is being modified or upgraded. Initially, access to an old version of a table is enabled and provided to a user. A copy of the old version is generated. Access is asynchronously redirected from the old version to the copy of the old version. A new version of the table is generated by modifying the structure of the first version of the table. The copy of the old version is accessible when the database is being modified or upgraded. When the structure is being modified, access is asynchronously redirected from the copy of the old version to the new version.

Abstract: Revocation of a zero downtime upgrade of an upgrade procedure of a source system to a target system is initiated. Thereafter, upgrade activities are stopped at the target system and production activities are stopped at the source system. At least a portion of the target tables can be subsequently dropped and any associated table structure changes can be revoked. At least a portion of the target tables are then switched from use by the target system to use by the source system. Next, the source system is connected to the source database schema to enable use of the source system in its state prior to the initiation of the upgrade procedure. Related apparatus, systems, techniques and articles are also described.

Abstract: A zero downtime upgrade procedure upgrading a source system to a target system is initiated that prepares software for the target system in parallel to the operation of the source system. As part of the upgrade procedure, source tables of the source system are renamed. Thereafter, the renamed source tables are cloned for the target system. Further, the renamed source tables are equipped with database triggers to transfer data from the renamed source tables to the cloned tables used by the source system according to a source database schema. Next, the target tables are generated that include updated software content for later use by the target system while the source tables are used via a bridge database schema. Tables can then be shared between the source database schema accessed via the bridge database schema and the target system.

Abstract: Revocation of a zero downtime upgrade of an upgrade procedure of a source system to a target system is initiated. Thereafter, upgrade activities are stopped at the target system and production activities are stopped at the source system. At least a portion of the target tables can be subsequently dropped and any associated table structure changes can be revoked. At least a portion of the target tables are then switched from use by the target system to use by the source system. Next, the source system is connected to the source database schema to enable use of the source system in its state prior to the initiation of the upgrade procedure. Related apparatus, systems, techniques and articles are also described.

Abstract: In one general aspect, a computer system can include instructions stored on a non-transitory computer-readable storage medium. The computer system can include a logging table generator configured to generate a logging table corresponding with an original table targeted for an upgrade, and a control table generator configured to generate a control table configured to store a version identifier for changes logged in the logging table. The computer system can include a change recorder configured to receive an indicator of a change to a record of the original table during execution of at least a portion of the upgrade of the original table, and a key recorder configured to store in the logging table a primary key identifying the record of the original table and the version identifier stored in the control table.

Abstract: A computer system can include a database comparator configured to identify a first database object from an original system for a complete modification based on a comparison of the first database object with a plurality of target upgrade database objects, and configured to identify a second database object from the original system for a partial modification based on a comparison of the second database object with the plurality of target upgrade database objects. A complete modification module can be configured to designate, in response to the identification of the first database object, the first database object for the complete modification based on an incremental conversion process. A partial modification module can be configured to designate the second database object for the partial modification based on the incremental conversion process when an instruction to implement the partial modification satisfies at least a portion of a modification condition.

Abstract: The present disclosure describes methods, systems, and computer program products for providing multi-level user interface theming.

Abstract: An original schedule module configured to receive an original schedule configured to trigger execution of a first original batch of entries including a set of object modification methods and a corresponding set of database objects before triggering execution of a second original batch of entries including a set of object modification methods and a corresponding set of database objects. An analysis module can be configured to determine logic for execution of each entry from the first original batch of entries based on the original schedule. A schedule generator can be configured to define, based on the logic for execution and based on the original schedule, a modified schedule configured to trigger parallel execution of a first modified batch of entries including less than all of the first original batch of entries, and a second modified batch of entries including less than all of the second original batch of entries.