Sap Se

Sap Ag

Kerstin Hoeft

Volker Driesen

Christian Stork

Welf N Walter

Michael Tsesis

Uwe Schlarb

Andrea Neufeld

Immo-Gert Birn

Cornelia Haase

Jens Lieberum

Martin Mayer

Helmut Prestel

Andreas Blumenthal

Reiner P Hammerich

Reiner Singer

Ulrich Auer

Marcel Hermanns

Steffen Meissner

Ralf-Juergen Hauck

Rolf Hammer

Andreas Simon Schmitt

Kai Baumgarten

Heiko Konrad

Dirk Debertin

Thomas Raupp

Tobias Wenner

Ralf Wendelgass

Sigrid K Wortmann

Matthias Schwarz

Michael Brombach

Jemin Tanna

Ulrich Koch

Florian Thomas

Harald Kuck

Steffen Weinstock

Andreas Gruenhagen

Christian Hansen

Frank Becker

Hartwig Brand

Bernd Roedel

Carsten Dietze-Selent

Peter Goebbels

Thomas Beissel

Uwe Hommel

Jens Otto

Michael Schafft

Methods, systems, and computer-readable storage media for providing a first access schema in a view layer of the database system, the first access schema including first database objects and projection views, each projection view corresponding to a second database object of second database objects in a data persistency, transitioning access of sessions of an application from the data persistency to the first access schema, executing at least a portion of the maintenance procedure in the database system, the at least a portion of the maintenance procedure changing one or more second database objects within the data persistency, creating a second access schema, and transitioning access of the sessions of the application from the first access schema to the second access schema, transitioning access of the sessions of the application from the second access schema to the data persistency, and removing the second access schema from the database system.

Using view layer in database system for zero downtime upgrade

Implementations include a first application server interacting with a first infrastructure table of a first version through a first access schema, providing, during an upgrade, a second application server to execute a portion of the upgrade by interacting with data schema through the first access schema, adjusting a structure of a second infrastructure table to provide an adjusted structure, the structure of the first version and the adjusted structure of the second version, the second infrastructure table including a copy of the first infrastructure table, providing a second access schema of the second version, providing a third application server configured to interact with data schema through the second access schema, and activating, by the third application server using an activator of the second version, objects of the second version, the activator including features that are different than an activator of the first version.

Zero downtime upgrade through delta deployment procedure using target software stack

Implementations include, during development of a second version within a development environment, tracing activities to determine development tables, the second version including changes that are incompatible with the first version, the development tables including deploy tables, activation tables, and troubleshooting tables, computing, by a configuration generator, an upgrade configuration based on the development tables, the upgrade configuration defining tables to deploy the changes during an upgrade, the tables being computed based on the development tables, during the upgrade: continuing production use of a first version using a first runtime at least partially including a first data schema, and establishing a second runtime at least partially by defining a second data schema within the database system using the upgrade configuration, the second data schema including the tables, and completing the upgrade by switching production use to the second version from the first version.

Configuring zero-downtime upgrades using automated development and test analysis

The present disclosure teaches solutions for transitioning between database system sharing types. In one example, a tenant container includes a read-only table, a first writable table, and a mixed table for storing read-only and writable data. When transitioning to a sharing setup, a shared container is created and a shared table is created in the shared container. Data is copied from the read-only table to the shared table and the read-only table is dropped. A read-only view is created in the tenant container and a second shared table is created in the shared container. Read-only mixed data is copied from the mixed table to the second shared table and deleted from the mixed table, and after the deletion, the mixed table is renamed as the second writable table. A union view is created that provides unified access to the second shared table and the second writable table.

Transitioning between system sharing types in multi-tenancy database systems

The present disclosure teaches solutions for patching content in database systems. In one example, a deployment package for an upgrade of a database system to a new system is received, and the content is deployed to a shared container. Shared objects are identified that are completely stored in the shared container, and partially-shared objects are identified where those objects have a shared portion in the shared container and a tenant portion in one or more tenant containers. First shared content is determined for the shared objects, while second shared content is determined for partially-shared objects. The first and second shared content is then deployed to the shared container. Local content is determined for the partially-shared objects and is deployed to each tenant container. Local content is then identified for local objects and is also deployed to each respective tenant container. Accordingly, both shared and tenant content is deployed.

Patching content across shared and tenant containers in multi-tenancy database systems

The present disclosure involves systems, software, and computer implemented methods for enabling multiple system sharing types in multi-tenancy database systems. One example method includes determining a system sharing type configuration for a database system. The system sharing type configuration is one of standard, shared, tenant, or simulated. Tables are created in the database system based on the system sharing type configuration and the table sharing type of each table. Content is deployed to created tables in the database system based on the system sharing type configuration and the table sharing type of each table. Access is provided to at least one application to the database system based on the system sharing type configuration and the table sharing type of each table.

System sharing types in multi-tenancy database systems

A table can be replaced with a view transparently to the application. For example, a data dictionary can specify that the view is to be substituted for the table. At runtime, application operations on the table are redirected to be performed on the view. Validation can be performed to ensure congruence between the table and the view. Can be useful for situations where a view with enhanced functionality is desired to be used in place of the table without re-coding the application.

Transparent database table replacement

In one embodiment, a method includes defining a parent structure including an extension. A polymorphic structure is defined for the extension. The polymorphic structure is associated with a plurality of client specialization structures, each client specialization being associated with a client in a plurality of clients. During runtime by a computing device, the parent structure is generated with an extension to a client specialization structure associated with one of the plurality of clients where client specialization structures associated with other clients are not visible to the parent structure.

Generic boxed components for multi-client systems

A new query language can be embedded in a business application programming language (e.g., the ABAP language). A query language consistent with implementations of the current subject matter can be based on a graph data-model of connected business objects (BO) or other data objects and can be designed as an efficient query language embedded into the business application programming language runtime, thereby allowing expression of business logic in a declarative manner.

Advanced business query language

A system, a method, and a computer program product for in-memory database processing are provided. A business object is generated in a first system. The generated business object is replicated from the first system to a second system. A high performance application implementing the replicated business object is executed based on at least one system specific view.

Systems and methods for in-memory database processing

Techniques for optimizing a software application include receiving, at a local computing system, a query from an application for data stored on a database table, the query including a context defined by a name of the database table; comparing the context of the query to a context of a predefined query scenario; based on the context of the query matching the context of the predefined query scenario, retrieving data stored on a secondary database replicated from data stored on a main database; and passing the retrieved data from the secondary database to the application.

Optimizing software applications

An application may obtain a data object based on a data type from a data dictionary. The obtained data object may be copied and modified. The modifications may include, for example, adding, removing, and/or changing a property, built-in type, simple type, and/or complex type of the data object.

Active and modifiable data dictionary

A system and method to provide a data dictionary cache in a distributed system is disclosed. An application server may include a data dictionary broker agent to provide an interface between an underlying data dictionary and an application. The application server may also include one or more data dictionary caches to provide efficient access to frequently requested system information.

System and method for a data dictionary cache in a distributed system

A server system may include a data dictionary to store platform-independent data types. A development client may access and modify a platform-independent data type stored in the data dictionary. The server system may notify other development clients using the data type that the data type has been modified.

Platform-independent data dictionary

Growing community of inventors

Wiesloch, Germany

Kerstin Hoeft