Abstract: A transaction processing protocol for serverless database management systems can use a transaction scheduler to guarantee consistent serializable execution though analysis of the access pattern of transaction types and appropriate ordering of the transaction's events at runtime. A transaction topology is determined for each type of transaction and these are combined and used to generate a serialization graph. Cycles in the serialization graph are identified and breaking transaction types which may break the cycles are determined. When transaction requests are received, a breaking type of transaction is scheduled as a last transaction in the current epoch and later transactions not having the breaking transaction type are scheduled to execute in the next epoch.

Abstract: The present disclosure involves systems, software, and computer implemented methods for data confidentiality-preserving machine learning on remote datasets. An example method includes receiving connection information for connecting to a remote customer database and storing the connection information in a machine learning runtime. Workload schedule information for allowable time windows for machine learning pipeline execution on remote customer data of the customer is received from the customer. A determination is made that an execution queue includes a machine learning pipeline during an allowed time window. The connection information is used to connect to the remote customer database during the allowed time window. Execution is triggered by the machine learning runtime of the machine learning pipeline on the remote customer database. Aggregate evaluation data corresponding to the execution of the machine learning pipeline on the remote customer database is received and provided to a user.

Abstract: Aspects of the current subject matter are directed to a user-facing approach for migration of unstructured data. A graphical user interface is provided to enable a user to execute a migration process of attachments between content repositories, where the execution is end to end with simple commands and/or user actions through interaction with the graphical user interface. The commands and/or user actions are translated into a background execution of the steps of the migration process in the proper order with proper parameters. Aspects of the current subject matter provide for the migration process to be transparent to the end user. Logs or reports relating to the migration process may be available and accessible to the user.

Abstract: Various examples are directed to systems and methods for operating a database management system (DBMS) in a cloud environment. An assembly worker executing at a first computing device may provide a first database protocol message generated by a process code executing at the first computing device. A translation engine executed at the cloud environment may translate the first database protocol message from a first format to a second format associated with a DBMS instance executing at the cloud environment to generate a translated first database protocol message. The translation engine may cause the translated first database protocol message to be provided to the DBMS instance and may receive, from the DBMS instance, a first reply corresponding to the translated first database protocol message. The first reply may be sent to the process code.

Abstract: A method may include receiving a definition of a table user-defined function (TUDF) in a graph query language. The table user-defined function may be created based on the definition. For example, the creation of the table user-defined function may include checking and compiling the definition to generate executable code associated with the table user-defined function. Upon receiving a query including a relational query language statement invoking the table user-defined function, such as a structured query language select statement, the query may be executed on at least a portion of a graph data stored in a database. The executing of the query may include calling the executable code to execute the table user-defined function included in the relational query language statement. Related systems and computer program products are also provided.

Abstract: A method for processing non-standardized data in a relational database may include identifying, within a sequence of operations forming a query pipeline for executing a query, a first operation ingesting a non-standardized data. In response to identifying the first operation ingesting the non-standardized data, a second operation may be inserted before the first operation. The non-standardized data may be output by a third operation preceding the first operation or a source external to the query pipeline. The second operation may serialize the non-standardized data for ingestion by the first operation, for example, by generating a relational table populated by the non-standardized data. The query may be executed by performing the sequence of operations included in the query pipeline. Related systems and computer program products are also provided.

Abstract: Methods and systems are disclosed for enumeration of trees in a database environment. Temporary copies of trees are stored in a database accelerator environment, for efficient access by software programs operating within the database layer. Multiple trees can be enumerated concurrently using level-by-level traversal. Nodes are assigned sortable indices through which a tree structure is maintained. Enumeration supports linking from a node of a parent tree to a child tree stored separately. Enumeration supports synthesizing child nodes in order to satisfy constraints on a parent node. Filtering and sorting are supported. The disclosed technology provides unexpectedly superior results, and can be applied in many fields. Variants are disclosed.

Abstract: Technologies are described for automated payload testing of open data protocol (OData) application programming interfaces (APIs). For example, metadata describing an OData service can be retrieved from the OData service. The OData service can then be tested for one or more entities of the OData service. Testing can be performed by dynamically creating various payloads for testing the entities of the OData service and the OData operations supported by the entities. Results of executing the payloads can be received and evaluated to determine whether a given payload was executed successfully by the OData service. Results of the testing (e.g., indications of success or failure) can be output.

Abstract: Various embodiments for a triple integration and querying system are described herein. An embodiment operates by identifying a plurality of triples corresponding to a knowledge graph, and generating a table in a database into which to import the set of triples. The table includes a subject column, a predicate column, and multiple object columns across different datatypes. Values from the triples of the knowledge graph are loaded into the table and a query is executed on the table.

Abstract: The present disclosure provides techniques and solutions for defining, deploying, or using distributed neural networks. A distributed neural network includes a plurality of computing elements, which can include Internet of things (IOT) devices, other types of computing devices, or a combination thereof. At least one neuron of a neural network is implemented, for a given data processing request using the distributed neural network, on a single computing element. Disclosed techniques can manage data processing requests in the event of an unreachable computing element, such as by processing the request without the participation of such computing element. Disclosed techniques also include redefining distributed neural networks to replace an unreachable computing element.

Abstract: A method includes receiving, at a search toolbar, a search query from a machine in a network. The machine has an associated machine profile for participating in the network as an entity. The machine profile includes a machine identifier and machine metadata. A query type is determined from the search query. A search context for the machine is determined using a semantic graph of the network. From a set of services for the network, one or more relevant services to respond to the search query are identified based on the query type and the search context. The search query is applied to the one or more relevant services to obtain a set of responses. A set of relevant results for the search query is determined from the set of responses. The set of relevant results is transmitted to the machine.

Abstract: Techniques and solutions are described for defining and deploying application content. Content, such as objects, can be created in a repository defined for a first application. A package can be defined based at least in part on the objects for use in a computing environment only requiring the first application. A second package can be defined based at least in part on the objects for use in a computing environment in which both the first application and a second application are available. Content can be moved between repositories defined for a single application and repositories defined for multiple applications. Content can be added to, or removed from, a client computing system as applications available on a client computing system change.

Abstract: Techniques and solutions are described for storing and processing metadata. A target system sends a request to a source system to identify extensions to one or more specified database artefacts. The source system identifies one or more software objects that include metadata extensions to the one or more specified database artefacts and sends at least a portion of such metadata elements to the target system in response to the request. The source system can expose APIs, such as APIs in a standard format, to the target system to assist in requesting and retrieving metadata from the source system.

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

Abstract: Disclosed herein are system, method, and device embodiments for implementing semantic discovery. An embodiment operates by retrieving a plurality of entities from a database instance. A semantic graph representation of the plurality of entities is generated within a graphical user interface. Context information is received from a user. A focus node is determined from the plurality of nodes using the context information. A semantic context of the focus node is determined, wherein the semantic context includes the focus node, a subset of the plurality of nodes, and subset of the plurality of edges. Responsive to the receiving, a visual indication of the semantic context is displayed within the graphical user interface.

Abstract: Techniques for integrating applications using a container image of an integration flow are disclosed.

Abstract: Techniques and solutions are described for providing flexible access to data during execution of a data access request. Multiple instances of a data artifact are created, where different instances of the data artifact provide access to different data sources having data associated with the data access request. When a data access request is executed, a particular data artifact instance can be used during execution of the data access request. In some cases, switching logic can be used to determine which data artifact instance is to be used in executing the data access request. Also described are technologies for facilitating creation of data artifact instances corresponding to a modelling artifact.