Sap Se

Sap Ag

Arne Harren

Simon Lueders

Alexander Bunte

Jonathan Bregler

Andreas Kellner

Volker Sauermann

Daniel Kuntze

Michael Schnaubelt

Le-Huan Stefan Tran

Vladislav Leonkev

Volker Driesen

Michael Wintergerst

Martin Mayer

Cornelia Kinder

Christopher Schildt

Peter Eberlein

Ulrich Auer

Tobias Elfner

Maciej Kabala

Timm Falter

Ralph Debusmann

Klaus Kopecz

Klaus Kretzschmar

Andreas Thumfart

Markus Eble

Philipp Becker

Ivan Galkin

Vaidas Gasiunas

Andre Hildebrandt

Stefan A Baeuerle

Franz Faerber

Anil Kumar Goel

Ralf Schmelter

Meinolf Block

Helmut Prestel

Rolf Hammer

Torsten Ziegler

Norbert Kuck

Gerd G Forstmann

Kai Baumgarten

Frank-Martin Haas

Carsten Binnig

Christiane Kettschau

Matthias Jensen

Till Westmann

Jens Lieberum

Stefan Kain

Kilian Kilger

Marco Haupt

Diego Sebastian Will

Minh-Khanh Do

Roger Killian-Kehr

Methods for using SQL statements to access an application-server-managed database are disclosed herein. In some embodiments, a user sends, either directly or indirectly (i.e., remotely) a SQL statement from an ODBC application or server, respectively, to an application server that preprocesses SQL statements for accessing data from a centralized database. The application server may have a SQL endpoint, and access to the SQL endpoint may be determined by a user's logon credentials, a user's presentation of a SAML token, or a user's presentation of a valid certificate. The application server may then parse the SQL statement and determine the user's authorization to access certain objects in the centralized database based on a SQL handler design-time configuration. A result from the statement may be sent back to the user either directly or indirectly and exposed.

Dedicated SQL services for cross-system SQL access to an application-server-managed database

A container group is created using a database deployment infrastructure (DI) administrator (HA). API privileges for the container group are granted, using the HA, to a container group administrator (GA). API privileges for a container created in the container group using the GA are granted, using the GA, to a container administrator (CA). API privileges for the container are granted, using the CA, to a container developer (CD). Schema privileges for the container are granted, using the CA, to a container consumer (CC). API privileges for the container group are revoked, using the HA, from the GA. The container group is dropped using the HA.

Database-level container group management

Disclosed herein are system, method, and device embodiments for consuming application-owned database objects via an API schema. An embodiment operates by determining that an application-owned database object is classified as API exposable, creating an API schema for proxy access to database objects that have been identified as API exposable, generating an API object within the API schema based on assigning the database object to the API schema, and providing, via the API schema and independent of the application, access to the API object by a privileged consumer.

Consuming application-owned database objects via SQL

Systems and methods are disclosed for connection multiplexing in a parallel processing environment. An example method includes requesting, responsive to a request to perform multiple database operations in a single transaction, a connection identifier for a physical connection to the database, providing the connection identifier to each of a plurality of workers, and performing the multiple database operations using the plurality of workers. Each worker may obtain a work item from a work queue, initiate a database request for the work item, and provide the database request to a database server. The database request represents one of the multiple database operations and includes the connection identifier. The database server may determine that the connection identifier corresponds to the physical connection, add the request to a connection queue associated with the physical connection, and execute requests from the connection queue against the database via the physical connection.

Connection multiplexing for a parallel processing environment

Parameter-based deployment control for database objects is provided, in which processes for deploying database artifacts into a database as database objects are implemented. Many different techniques may be used in executing such deployment processes, including whether and how to combine various deployment-related jobs, identify/record/assess/correct potential errors, govern or instruct artifact conversion operations, or generally manage available resources with respect to executing the deployment(s) efficiently. By providing for selectable parameter values that are executed in an efficient, e.g., hierarchical, manner, deployment procedures may be implemented in a highly efficient and customizable manner.

Parameter-based deployment control for deployment of database artifacts

A computer-implemented method for exporting a database container from a database includes exporting database container metadata including artifact definitions in the metadata along with the actual metadata content to a database management system, exporting the database container including the database objects deployed therein to the database management system. The exporting of the database container includes exporting dependencies and structures of the database objects deployed therein, but not the actual content of the database objects. In some instances, however, exporting of the database container can include exporting the actual content of the database objects in response to user request. The method further includes packing the exported database container metadata and the exported database container in an archive. The data in the archive can be unpacked in substantially reverse order to import the database container into another database.

Exporting and importing database containers

In an example embodiment, a new development infrastructure is provided that provides an external repository for database definitions. The development infrastructure also then includes a development mode. When using the development mode, the behavior of the development infrastructure is modified to better fit the development of database artifacts. The developer uses a development base version of a definition (usually the latest released version of the definition) but also creates migrations that indicate how the development base version should be modified to arrive at the developer's intended new definition. While still in development mode, the deployment may be run, which causes data in the development mode that uses the old definition to be dropped and replaced by the base version. The development mode then executes the specified migrations.

Deployment of automated migrations for database tables

Systems and methods are disclosed for automatically detecting a connection status in an asynchronous processing request. An example method includes obtaining, at a processing client and responsive to a first request from a requesting client to perform a plurality of database operations in a single transaction, a connection identifier for a connection to a database on a database server, the connection to be used to execute the plurality database operations and storing the connection identifier in a row of a status table. In some implementations the existence of the row indicates the status of the connection is active. In some implementations the row includes a flag indicating the status. The method also includes providing the connection identifier to the requesting client, receiving a second request from the requesting client, the second request being for a status of the connection, determining the status using the status table.

Automatic status detection for an asynchronous processing request

A computer-implemented method for deploying a new artifact file in a database. The new artifact file provides specifications for one or more new run-time database objects to be created in the database by processing of the new artifact file by artifact-type specific conversion engines. The method includes assigning ownership of the one or more new run-time database objects to be created in the database to the new artifact file, and, when an existing database object in the database provided by another artifact file corresponds to a new run-time database object specified in the new artifact file, assigning ownership of the existing database object in the database to the new artifact file being deployed.

Ownership transfer of database artifacts between files

Methods, systems, and computer program products for accessing a database element are described. A local schema comprising a table link is created and the table link is used to access a database table via a persistency interface.

Database public interface

A first instance of a deployer application is executed in a server mode. The deployer application is configured to deploy service instances for a multi-tenant application. A first onboarding request is received for a first tenant for the multi-tenant application. A first service instance for the first tenant is created, in response to the first onboarding request. A first request to deploy artifacts to the first service instance is received, by the first instance of the deployer application. The artifacts are deployed, by the first instance of the deployer application, to the first service instance.

Artifact deployment for application managed service instances

A dependency graph is generated for database files. An unvisited node of the dependency graph is selected and a breadth-first-search performed starting from the selected unvisited node. Results of the breadth-first-search is defined as a group. A group assignment for the database files is returned.

Deployment of independent database artifact groups

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

Growing community of inventors

Walldorf, Germany

Arne Harren