Sap Se

Daniel Kuntze

Volker Sauermann

Arne Harren

Simon Lueders

Alexander Bunte

Jonathan Bregler

Andreas Kellner

Le-Huan Stefan Tran

Michael Schnaubelt

Vladislav Leonkev

Michael Wintergerst

Cornelia Kinder

Christopher Schildt

Ralph Debusmann

Andreas Thumfart

Andre Hildebrandt

Stefan A Baeuerle

Anil Kumar Goel

Meinolf Block

Klaus Kopecz

Roger Killian-Kehr

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

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

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

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

Embodiments map from a database environment, dependencies between files created at designtime and corresponding runtime data objects defined by deployment of those files. A dependency table is populated with dependency information (e.g., origin, target, dependency type) extracted during deployment. That dependency information may be searched according to user-specified parameters (e.g., a file provides an object; an object requires a file), to allow rapid correlation between designtime file(s) and related runtime data object(s). Embodiments are particularly useful in visualizing complex (e.g., one-to-many; many-to-one) file-object dependencies characteristic of modern database environments. Queries posed to the dependency table may further seek intra-designtime dependency information (e.g., one file depends upon another file; one file impacts another file), and/or intra-runtime dependency information (e.g., table objects referenced by view objects; view objects referenced by procedure objects). Dependency information may be recursively searched in an iterative manner in order to construct dependency pathways reflecting complex file-object relationships.

Dependency mapping in a database environment

Whether database objects corresponding to an artifact to deploy already exists in a database is determined. Depending artifacts are calculated using a prior-generated dependency graph. Whether any database objects corresponding to the calculated depending artifacts need to be redeployed are determined. Whether a build plugin corresponding to the database objects needing to be redeployed supports a redeployment option is determined. The artifacts are processed according to an execution graph.

Optimized re-deployment of database artifacts

A database includes a run-time database container, which provides an isolated computing environment for a database object deployed therein. The database further includes a public synonym object outside the run-time database container in the database. The public synonym object is associated with the database object deployed inside the run-time database container and provides external access to the database object deployed inside the run-time database container independent of the location of the run-time database container.

External access to database container artifacts

An external database schema permitted to be accessed from a container using a database synonym is determined. A logical schema representing the external database schema is defined. A synonym for the container is defined using the logical schema and an object associated with the external database schema. The logical schema and synonym is deployed to the container using a logical schema plugin. The container is configured to disable the logical schema plugin and to only allow references to the defined logical schemas.

Restricting access to external schemas from within a database level container by whitelisting allowed schemas

An import configuration section of a file is identified, where the import configuration identifies a database table. Key specifications of the database table are reserved based on the import configuration. A first and a second Boolean flag parameter associated with the database table is identified. A determination is made that i) a value of the first Boolean flag indicates importing of entries from the file into the database table is allowed, and that ii) a value of the second Boolean flag indicates removal of entries of the database table is allowed. In response to the determining entries are removed from the database table corresponding to the key specifications, and entries are imported from the file into the database table corresponding to the key specifications.

Reserving key specifications

Systems and methods deploy artifacts to a database in a self-organizing matter as a single transaction. An example method includes determining one or more root nodes in a dependency graph, the dependency graph including a node for each of the plurality of artifacts, each node having a respective dependency count, wherein the one or more root nodes have a respective dependency count of zero. The method also includes generating a work item for each of the root nodes and placing the work item in a work queue. In such a method, a plurality of workers can pop work items off the work queue in parallel and initiate deployment of the artifacts represented by the work items. Each worker of the plurality of workers can also reduce by one the dependency count of nodes in the dependency graph that are successor nodes of the root node deployed using the worker.

Growing community of inventors

Bruchsal, Germany

Daniel Kuntze