Sap Se

Sap Ag

Juergen Specht

Volker Driesen

Steffen Meissner

Lars-Eric Biewald

Martin Mayer

Heiko Konrad

Christoph Luettge

Stefan A Baeuerle

Joachim Fitzer

Juergen Sattler

Uwe Schlarb

Martin Hartig

Bernhard Thimmel

Wieland Hoprich

Olaf Meincke

Matthias Lehr

Thomas Ullrich

Karsten Fanghaenel

Andre Haferkorn

Matthias Mittelstein

Erwin Burkhardt

Ioannis Grammatikakis

Andrey Engelko

Hilmar Demant

Markus Viol

Jan Heiler

Ralf-Juergen Hauck

Sebastian Droll

Frank Schertel

Nicolai Jordt

Thorsten Weber

Ye Jin

Joerg Schoen

Christian Lutter

Methods, systems, and computer program products for converting a database table and implementing upgrades and/or migrations are described. A bridge schema comprising a bridge view for a table in a database of an original schema is created and a bridge application server instance is created, the bridge application server instance configured to utilize the bridge schema to access the table of the original schema. The table of the original schema is revised to conform to a specified target schema and a target application server instance configured to access the revised table is created.

Database table conversion

Methods, systems, and computer-readable storage media for deploying upgrade packages during zero downtime upgrade of production systems include actions of receiving an upgrade package, the upgrade package defining one or more changes to be deployed to a system that has already undergone partial deployment during a zero downtime upgrade, and including one or more objects having respective object types, receiving a deployment configuration, the deployment configuration providing a plurality of lists of object types for respective constraints and, for each list of object types, specifying a deployment option for object types in the respective list of object types, determining a set of object types included in the upgrade package, the set of object types comprising one or more object types, and selectively permitting deployment of the upgrade package to execute the one or more changes based on the set of object types and the plurality of lists of object types.

Zero downtime maintenance in constrained systems

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

Implementations include providing a database system that a plurality of tenant systems interact with, providing a shared database schema and a plurality of tenant database schemas, the shared database schema including a shared table, and each tenant database schema being assigned to a respective tenant and including a view into the shared table, which includes a tenant specification field, and a row visibility field, the tenant specification field indicating a tenant, to which a respective row is assigned, and the row visibility field indicating visibility of a respective row to respective tenants.

Tenant table sharing with content separation

Methods, systems, and computer-readable storage media for data migration in a maintenance procedure executed on a software system include actions of initiating the maintenance procedure, and determining that an instance of a data migration object is included in a list of deployed transport objects, and in response: reading a migration class from the data migration object, determining at least one table of a database that is affected by the maintenance procedure based on one or more methods of a first interface of the migration class, receiving, using a second interface of the migration class, data migration logic including computer-executable instructions to migrate data, and executing the data migration logic to affect the at least one table.

Multi-procedure support in data migration

A system includes a first and a second storage device and a computing device. A set of partitions includes a first subset of partitions and a second subset of partitions. The first storage device stores the first subset of partitions. The second storage device stores the second subset of partitions. The computing device is configured to execute an iterative update of a selected partition until a fully updated partition is generated. The updated partition generated in a current iteration is used as a selected partition in the next iteration, and a not yet updated partition is updated in every next following iteration.

Database system and method of operation thereof

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

A zero downtime upgrade procedure is initiated that upgrades a first version of software executing on a source system comprising at least one source server to a second version of software executing on a target system comprising at least one target server. The source system initially starts operating in a read-write mode. Thereafter, concurrent with the operation of the source system, operation of the target system is initiated in a read-only mode. Operations of the source system are then ceased by ramping down activities of the source system. Upon cessation of operation of the source system, operation of the target system is initiated in a read-write mode.

Zero downtime software system upgrade

Implementations include actions of initiating a procedure on an application that interacts with a database system having a start schema, through which a first version of the application interacts with tables, providing a bridge schema including table views to each table of the start schema, switching a first version of the application to interact through the bridge schema, creating a shadow field in a table, the shadow field corresponding to a field of the table that is to undergo a change during an upgrade from the first version to a second version, providing a trigger in the start schema, the trigger executing a transformation between the field and the shadow field during the upgrade, modifying the table in the start schema to a target structure to change a parameter of the shadow field or the field of the table, and switching the second version to interact through the start schema.

A zero downtime upgrade of a source system to a target system is initiated. The source system and the target system operate in a first database layer and a second database layer. Thereafter, differences in structure and/or database type are computed between a source table in the source system and a target table in the target system in each of the two different database layers. The data is then migrated, using the computing differences and in the second database layer, from the source table to the target table. The upgrade procedure is later terminated after completion of the migration of the data. Related apparatus, systems, techniques and articles are also described.

Handling table deltas during zero downtime upgrade

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

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.

Growing community of inventors

Gerabronn, Germany

Juergen Specht