Abstract: 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.

Abstract: 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.

Abstract: Systems and techniques for performing a simulated deployment to a database include generating a dependency graph of multiple artifacts contained in a container for deployment to a database and receiving an indication to perform a simulated deployment of the artifacts. In response to receiving the indication, the container is marked for simulated deployment. The artifacts are deployed to the database using the marked container and the generated dependency graph without committing the artifacts to the database. The deployed artifacts are rolled back such that no state changes are made to the database due to the simulated deployment.

Abstract: Context tracing may be implemented by modifying a call to parameterize, and thereby govern, logging operations of a called software application or program. Resulting messages of the logging operations are stored in a manner that facilitates fast identification and retrieval of the messages. Accordingly, accurate identification of errors or sub-optimal operations of the called software application or program is enabled, thereby enabling correction and/or optimization of operations of the called program.

Abstract: 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.

Abstract: 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.

Abstract: A system, a method, and a computer program product for deployment of objects are disclosed. At least one configuration for deploying of at least one artifact during runtime of an application is defined. The configuration includes at least one dependency for the artifact. The configuration is applied to the artifact. The artifact is deployed based on the applied configuration during runtime of the application. The configuration can include at least one of the following: a default configuration for the artifact and an explicit configuration for the artifact.

Abstract: A system, a method, and a computer program product for deployment of objects are disclosed. At least one configuration for deploying of at least one artifact during runtime of an application is defined. The configuration includes at least one dependency for the artifact. The configuration is applied to the artifact. The artifact is deployed based on the applied configuration during runtime of the application. The configuration can include at least one of the following: a default configuration for the artifact and an explicit configuration for the artifact.

Abstract: A system, a method, and a computer program product for deployment of objects are disclosed. Using a deployment infrastructure of a database system, a deployment container for deployment of at least one object at runtime of an application is generated. The container includes at least one artifact for the object and a container schema indicative of at least one dependency associated with the object. At least one deployment privilege is associated based on the container schema with the artifact for the object. The artifact of the deployment container is deployed based on the associated deployment schema during runtime of the application. The container can be an isolated container and an access privilege to an object can be requested based on a synonym for deployment purposes.

Abstract: A system, a method, and a computer program product for deployment of objects are disclosed. At least one configuration for deploying of at least one artifact during runtime of an application is defined. The configuration includes at least one dependency for the artifact. The configuration is applied to the artifact. The artifact is deployed based on the applied configuration during runtime of the application. The configuration can include at least one of the following: a default configuration for the artifact and an explicit configuration for the artifact.

Abstract: A system, a method, and a computer program product for deploying objects are disclosed. A file containing a plurality of artifacts for deploying during runtime of an application is defined. At least one dependency for at least one artifact in the plurality of artifacts is determined based on the defined file. A database object for implementation during runtime of the application is created based on the determined dependency. At least one change to the database object during runtime of the application is implemented. The artifact is deployed during runtime of the application based on the implemented change to the database object.

Abstract: A system, a method, and a computer program product for deploying of objects are disclosed. At least one file containing a plurality of artifacts for deploying during runtime of an application is defined. Each artifact in the plurality of artifacts includes at least one object in the plurality of objects required to be deployed during runtime of the application. At least one dependency for at least one artifact in the plurality of artifacts is determined. An execution order for deployment of the plurality of artifacts is generated. The plurality of artifacts is deployed in accordance with the generated execution order.