Sap Se

Sap Ag

Ulrich Auer

Volker Driesen

Ralf-Juergen Hauck

Arne Harren

Uwe Schlarb

Martin Mayer

Christian Stork

Welf N Walter

Torsten Ziegler

Immo-Gert Birn

Hans-Juergen Hennrich

Ralf Belger

Kerstin Hoeft

Heiko Konrad

Peter Schreiber

Florian Thomas

Hans-Juergen Lattrell

Welf Walter

The present disclosure involves systems, software, and computer implemented methods for key pattern management. One example method includes receiving a query for a logical database table from an application. A determination is made as to whether the query is a write query. In response to determining that the query is a write query, a determination is made as to whether the query complies with a key pattern configuration that describes keys of records included in a physical database table that is part of a logical table implementation. The physical table includes records of the logical database table that are allowed to be written by the application. The write query is redirected to the physical database table in response to determining that the query complies with the key pattern definition. The query is rejected in response to determining that the query does not comply with the key pattern configuration.

Key pattern management in multi-tenancy database systems

Methods, systems, and computer-readable storage media for, in response to initiation of a deployment to a multi-tenant system, cloning a shared table in a shared container of a database system to provide a cloned table, the shared table corresponding to a plurality of table views in respective tenant containers, providing, within each tenant container of the tenant containers, an updated view to the cloned table, for a data object of the deployment, determining a previous location of the data object within the database system from an object catalog, and a new location of the data object within the database system from a deploy file, and storing the data object in one of the shared container, and a tenant container of a respective tenant based on one or both of the previous location, and the new location of the data object.

Change management for shared objects in multi-tenancy systems

In an example embodiment, a proxy object is delivered to a first schema having a first logical name and stored in the software object database, the proxy object referencing an object in a second schema having a second logical name. Any dependencies from the object in the second schema to the proxy object in the first schema are removed a cycle-free graph of dependencies between objects the software object database is generated. Objects are delivered the software object database using the cycle-free graph. A definition for the proxy object is created including the logical name for the first schema. The proxy object is delivered by replacing, at a time subsequent to the proxy object being delivered to the software object database, the logical name for the first schema stored in the definition with a physical name for the first schema.

Database proxy object delivery infrastructure

In an example embodiment, software objects of a first database type are delivered to a first schema having a first physical name and stored in the software object database. A definition is created for the first schema including a logical name for the first schema. The first schema is activated by replacing, at a time subsequent to the first schema being delivered to the software object database, the logical name for the first schema stored in the definition with a physical name for the first schema.

Database container delivery infrastructure

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 data separation and write redirection in multi-tenancy database systems. One example method includes providing access to at least one application to a database system. A query is received from an application. A determination is made that the query is associated with a union view that provides unified access to a first read-only table in a shared database container and a first writable table in a tenant database container. A determination is made as to whether the query is a read query or a write query. In response to determining that the query is a read query, the query is processed using the union view. In response to determining that the query is a write query, the query is modified to use the first writable table and the query is processed using the writable table.

Data separation and write redirection in multi-tenancy database systems

In an example embodiment, one or more changes to one or more objects in the software object database are received from a developer. A change list is generated based on the one or more changes. An object definition is exported for every object in the change list from a first schema in the database to a second schema in the software object database. A first object in the second schema is activated by mapping a logical schema name specified in the object definition for the first object to a corresponding physical schema name and creating or altering the first object in the second schema using the physical schema name.

Database object delivery infrastructure

The present disclosure involves systems, software, and computer implemented methods for exchanging shared containers and adapting tenants in database systems. One example method includes receiving a request to deploy a new version of a database system. A deployment package is received that includes new version data. A new shared container is installed in parallel to a current shared container. The new version is deployed to each of multiple tenant containers. Each of the tenant containers is individually linked to the new shared container, including dropping at least one view in each respective tenant container to shared content in the current shared container and adding at least one view in each respective tenant container to the updated shared content in the new shared container. Changed tenant content is deployed to each tenant container. The current shared container is dropped after deployment to each of the multiple tenant containers has completed.

Exchanging shared containers and adapting tenants in multi-tenancy database systems

In an example embodiment, relationships among a plurality of schemas are examined to remove any cyclic dependencies. Then a cycle-free graph of the cyclic dependencies is constructed. A first delivery mechanism is used to deliver software objects of a first database type to a first of the plurality of schemas in a software object database, using the cycle-free graph. A second delivery mechanism is used to deliver software objects of a second database type to a second of the plurality of schemas in the software object database, using the cycle-free graph.

Database object lifecycle management

In an embodiment, a method is provided for updating a computer program. In this method, a record related to a data structure being effected in the updating of the computer program is identified. Here, the data structure is accessible by the computer program. Additionally, a request is received during the update of the computer program to access a further record related to the data structure. The further record in the request is identified to match the record effected in the updating of the computer program. The request is thereby prevented from accessing the further record related to the data structure based on the further record matching the record related to the data structure

Handling data access requests in computer program updates

Described are methods and systems related to transporting one or more object packets present in a nested hierarchy of one or more system landscapes. The object packets available for transporting from source systems to target systems present in the nested hierarchy of the system landscapes is identified. A transport request is generate for a collection of object packets of each source system in the nested hierarchy of the system landscapes. The transport requests are aggregated to render a nested transport collection. The nested transport collection is transported within the nested hierarchy of the system landscapes. The nested transport collection is deployed to assign the transport requests present in the nested transport collection to the target systems present in the nested hierarchy of the system landscapes.

Transporting object packets in a nested system landscape

The subject matter disclosed herein provides methods and apparatus, including computer program products, for providing software updates. In one aspect there is provided a method. The method may include receiving software objects associated with a software update. Moreover, a container may be provided. The container may include the received software objects and attributes. The attributes may describe the software objects to configure transport to different applications. Related systems, apparatus, methods, and/or articles are also described.

Growing community of inventors

Hockenheim, Germany

Ulrich Auer