Sap Se

Lars-Eric Biewald

Juergen Specht

Volker Driesen

Steffen Meissner

Heiko Konrad

Wieland Hoprich

Thomas Ullrich

Andre Haferkorn

Martin Hartig

Martin Mayer

Andrey Engelko

Ralf-Juergen Hauck

Nicolai Jordt

Christoph Luettge

Joerg Schoen

Andrea Klein

Matthias Mittelstein

Stefan Runge

Implementations can include providing a snapshot table, replacing, in a first access schema, a first projection view with a union view, creating, in a second access schema, a snapshot projection view, a second projection view, and a set of database triggers, and during execution of an upgrade procedure that results in changes to records of the data table: recording the changes to the records of the data table in the snapshot table, for each record of the data table changed, providing the record in the snapshot table in an unchanged state through at least one database trigger and the snapshot projection view, and returning a set of records through the union view in response to a query, the set of records including a first sub-set of records of the data table and a second sub-set of records of the snapshot table.

Snapshot changes for cloud systems during zero downtime upgrades

A system and method for database migration is provided. In an example embodiment, the database migration technique may include execution modules having a first connection to a source database and a second connection to a target database, and orchestration modules adapted to identify first and second subsets of statements from a single storage table, wherein the first and second subsets of statements are executed by the execution modules during an uptime period of the source database.

Asynchronous SQL execution tool for zero downtime and migration to HANA

Various techniques are described for precisely locking database objects within a database during a system upgrade with the use of database freeze triggers. Some database freeze triggers can be utilized to lock transport requests while other database freeze triggers can be utilized to lock database objects such as exchange tables. For transport requests, techniques describe the use of a whitelist identify transport objects or transport object types which shall remain unblocked. As a result, a database freeze trigger can be generated for transport objects or transport object types that are not included in the whitelist. For database objects, techniques describe the identification of a tool or service which has been allowed during the upgrade. Database objects which can be modified during execution of the tool or service can be identified. Database freeze triggers can be generated for the database objects besides those identified.

Precision locking a database server during the upgrade of a system landscape

Methods, systems, and computer-readable storage media for applying corrections during an upgrade procedure of a software management system include actions of receiving a set of white-listed object types, receiving a set of corrections to be imported, the set of corrections including a set of objects, to which corrections are to be applied during the upgrade procedure, determining a set of object types included in the set of corrections, the set of object types including one or more object types, and selectively permitting one or more transport requests to effect corrections of the set of corrections to be issued during the upgrade procedure based on the set of object types and the set of white-listed object types.

Enabling corrections during upgrade procedure

Embodiments described herein relate to an improved technique for maintaining a consistent state during data migration operations in an active database system. Data can be copied from database table(s) of the active database system into a corresponding database table(s) in the shadow system. Snapshots of the active system can be taken at a specified point in time and used to establish a point of consistency. Later, the snapshot data can be compared with the data in the shadow database system. If the data matches, then the active and shadow database systems are at a consistent state and the data migration process completes. If the data does not match, embodiments are configured to restore the consistent state at the specified point in time by copying the snapshot data into the shadow database table(s).

Reverse snapshot clone

The present disclosure describes methods, systems, and computer program products for providing multi-level user interface theming. One computer-implemented method includes instantiating a shadow system and database schema for a new version software application in a shared database, the shadow system database schema containing aliases pointing to tables instantiated in a production database schema, instantiating a bridge database schema containing aliases pointing to each database table within the production database schema, preparing a bridge sub-system connected to the bridge database schema aliases, replicating database tables within the production database schema, for use by the bridge sub-system and adjusting the original database tables for structure and content consistent with the new version software application, deploying an upgrade sub-system and tools to complete adjustment of structure and content of the original database tables, and connecting an instantiated instance of the new version software application to adjusted database tables.

Zero downtime maintenance with maximum business functionality

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.

Data access management during zero downtime upgrade

Techniques for migrating data in a database include identifying an update to one or more data entries of a source table; determining that a status of a trigger associated with the source table indicates to update a logging table, and in response: updating, in a first transaction, (i) the one or more data entries of the source table, and (ii) one or more data entries of the logging table based on the user input, and copying content of the source table to a target table; and determining that the status indicates to update the target table, and in response: updating, in a second transaction, (i) the one or more data entries of the source table and (ii) one or more data entries of the target table based on the user input, and updating the content of the target table based on the one or more data entries of the logging table.

Migrating data in tables in a database

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.

Growing community of inventors

Mannheim, Germany

Lars-Eric Biewald