G06F16/256

Dynamic Query Allocation to Virtual Warehouses

Methods, systems, and apparatuses for managing and selecting virtual warehouses for execution of queries on one or more data warehouses are described herein. A request to execute a query may be received. An execution plan, for the query, may be identified. A processing complexity for the query may be predicted based on the query and the execution plan. A plurality of virtual warehouses may be identified. An operating status and processing capabilities of the plurality of virtual warehouses may be determined. A subset of the plurality of virtual warehouses may be selected based on the processing complexity, the operating status of the plurality of virtual warehouses, and the processing capabilities of the plurality of virtual warehouses. The query may be executed on one of the subset of the plurality of virtual warehouses.

Quiesce notifications for query retries

The subject technology retrieves information related to a set of instances of compute service managers, each instance of a particular compute service manager being associated with a set of virtual warehouses. The subject technology filters the information to determine a set of candidates from the set of instances of compute service managers. The subject technology sorts the set of candidates based at least in part on each workload of each of the set of candidates. The subject technology selects a candidate compute service manager from the set of instances of compute service managers to issue a query restart by randomly selecting an execution node, the execution node being included in a particular virtual warehouse associated with the candidate compute service manager, the selecting facilitating improving utilization of cluster resources and improving query execution on the selected candidate compute service manager.

SYMMETRIC QUERY PROCESSING IN A DATABASE CLEAN ROOM

First and second database accounts respectively share first and second source datasets with one another in a data clean room. The first database account stores a first approved-statements table that contains database statements that are permitted by the first database account to be executed against a combination of the shared first source dataset and the shared second source dataset. The second database account stores a second approved-statements table that contains database statements that are permitted by the second database account to be executed against the combination of the shared first source dataset and the shared second source dataset. One or more queries received from the first database account that are included in the second approved-statements table are processed, as are one or more queries received from the second database account that are included in the first approved-statements table.

Cluster instance balancing of a database system across zones

The subject technology selects a particular zone among multiple zones based on a target skew to meet a global balancing of cluster instances. The subject technology deploys a particular type of cluster instance to the particular zone. The subject technology, for each zone from the multiple zones, determines a respective number of cluster instances. The subject technology identifies a second particular type of cluster instance to remove based on a total number of the second particular type of cluster instance in the multiple zones and a second total number of the particular type of cluster instance in the multiple zones. The subject technology removes the second particular type of cluster instance from a second particular zone to meet the global balancing of cluster instances in the multiple zones.

Systems and methods for in-place records management and content lifecycle management
11550761 · 2023-01-10 · ·

An in-place information management system having a management application built on a common data model and configured for asynchronous query-based application of policies on content stored in the disparate data storage systems through a query interface which may be part of a set of integration services. The common data model may be configured based on common architectures of the disparate data storage systems. The query interface may be configured for running a query on a data storage system in response to a search request received by the management application from a records manager and for mapping semantically equivalent keys from disparate data storage systems to a key in the common data model. The query may define a set of records to be treated similarly according to corporate policy on content lifecycle and records compliance.

Contextual-characteristic data driven sequential federated query methods for distributed systems

Methods and systems are disclosed for a sequential federated query for information in a residential, commercial, and/or distributed system. A method of processing a sequential federated query for distributed systems may comprise receiving a sequential federated query; deconstructing the sequential federated query into query elements; identifying a Contextual-Characteristic Data Source (CCDS), a Transactional-Unstructured Data Source (TUDS), and a data organization parameter based on the query elements; generating a CCDS result data set from the CCDS based on the data organization parameter; processing the CCDS result data set to develop a TUDS query based on the data organization parameter; generating a TUDS result data set from the TUDS based on the developed TUDS query and the data organization parameter; generating a final sequential federated query data set based on the TUDS result data set and the data organization parameters; processing a formatted sequential federated query data set based on the processing of the final sequential federated query data set and the data organization parameter; and providing the formatted sequential federated query data set to a management system for action.

Systems for secure enterprise-wide fine-grained role-based access control of organizational assets

The disclosure is directed to systems and methods for enterprise-wide fine-grained role-based access control to a plurality of organizational assets. In various embodiments exemplary methods include receiving, via an authorization service client API, identification of an asset for fine-grained role-based access control; a definition of an asset type of the asset; a definition of an asset value; receiving, a definition of an organizational role with fine-grained role-based access control to at least one of the asset, the asset type, and the asset value. Furthermore, receiving permissions for fine-grained role-based access by the organizational role to at least one of the asset, the asset type, and the asset value. Furthermore, the exemplary method may comprise providing an authorization service user interface (UI) for enabling fine-grained role-based access control to the asset based on the fine-grained role-based access control database schema.

Query processing in a polystore

A method may include generating, based at least on an analysis plan, a logical plan, the analysis plan specifying one or more operations performed on data stored in a polystore that includes a first database management system and a second database management system. The logical plan may include a sequence of logical operators corresponding to the operators specified by the analysis plan. The generating of the logical plan may include rewriting the sequence of logical operators by at least reordering, replacing, and/or combining one or more logical operators in the sequence of logical operators. Candidate physical plans may be generated based on the logical plan. The analysis plan may be executed based on a physical plan selected from the candidate physical plans. Related systems and articles of manufacture are also provided.

SYSTEMS AND METHODS FOR DATA MANAGEMENT

Systems and methods for data management. In some embodiments, information may be accessed from a knowledge structure associated with an entity. The knowledge structure may store both private information of the entity and state information of a distributed ledger. For instance, the knowledge structure may include an identity structure for the entity and/or an attribute structure corresponding to an attribute of the entity. The identity structure may store a pointer to the attribute structure. Additionally, or alternatively, the attribute structure may associate a value with the attribute of the entity.

Search system and search method for finding new relationships between material property parameters

To effectively utilize knowledge of relationship information among material property parameters the users tangibly and intangibly have in a search system that generates a graph in which material property parameters are nodes and relationships of the material property parameters are edges from a database of material property parameter pairs whose relationships are already known, and conducts a path search in the generated graph. A search system, which includes the database, a graph generator that generates the graph, and a graph searcher searches the graph, further includes a user interface and a user information storage unit corresponding to each user. The user conducts a search unique to the user by inputting relationship information between the material property parameters that he has to the user information storage unit and integrating the relationship information into the above graph. Further, by accumulating a history of searches conducted by the user in the user information storage unit and analyzing the search history, the user can be provided with new knowledge.