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: 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: 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: 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: A computer-implemented method for modifying software code includes: processing a command to modify a first module of software code stored on a production system in a distributed computing environment, where the software code includes a first plurality of data objects and a first plurality of notes; generating at least one queue comprising the second plurality of notes; modifying a second module of software code stored on a development system in the distributed computing environment with the second plurality of notes, where the second module of software code comprising a version of the first module of software code; and transferring the second module of software code to the production system to modify the first module of software code such that the first plurality of notes are modified by the second plurality of notes.

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: 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: 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: A computer-implemented method for modifying software code includes: processing a command to modify a first module of software code stored on a production system in a distributed computing environment, where the software code includes a first plurality of data objects and a first plurality of notes; generating at least one queue comprising the second plurality of notes; modifying a second module of software code stored on a development system in the distributed computing environment with the second plurality of notes, where the second module of software code comprising a version of the first module of software code; and transferring the second module of software code to the production system to modify the first module of software code such that the first plurality of notes are modified by the second plurality of notes.

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