Sap Se

Immo-Gert Birn

Volker Driesen

Uwe Schlarb

Christian Stork

Welf N Walter

Andrea Neufeld

Ulrich Auer

Ralf-Juergen Hauck

Torsten Ziegler

Kerstin Hoeft

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

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 involves systems, software, and computer implemented methods for deploying changes to key patterns in database systems. One example method includes receiving a new shared container that includes a new key pattern for a logical split table and an updated read-only-portion physical table for a logical split table. The updated read-only-portion physical table includes records that match a complement of the new key pattern. Records that match the new key pattern are identified in the read-only-portion physical table of the logical split table in a current shared container. The identified records are moved from the read-only-portion physical table in the current shared container to a writable-portion physical table in a tenant container. Records not matching the new key pattern are deleted from the writable-portion physical table of the logical split table in the tenant container.

Deploying changes to key patterns 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

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

The present disclosure involves systems, software, and computer implemented methods for deploying changes in a multi-tenancy database system. One example method includes upgrading at least one tenant database container in a database system. Table structure differences and table sharing type differences are determined by comparing tables in a current-version shared container to tables in a next-version shared container. A current key pattern configuration in the current-version shared container is compared to an updated key pattern configuration in the next-version shared container to identify key pattern configuration differences. Each table in the at least one tenant database container is upgraded based on the table structure differences, the table sharing type differences, and the key pattern configuration differences.

Growing community of inventors

Philippsburg, Germany

Immo-Gert Birn