G06F16/24544

Dynamic performance tuning based on implied data characteristics

Techniques for improving system performance based on data characteristics are disclosed. A system may receive updates to a first data set at a first frequency. The system selects a first storage configuration, from a plurality of storage configurations, for storing the first data set based on the first frequency, and stores the first data set in accordance with the first storage configuration. The system may further receive updates to a second data set at a second frequency. The system selects a second storage configuration, from the plurality of storage configurations, for storing the second data set based on the second frequency, and stores the second data set in accordance with the second storage configuration. The second storage configuration is different than the first storage configuration.

Generating search commands based on cell selection within data tables

A search interface is displayed in a table format that includes one or more columns, each column including data items of an event attribute, the data items being of a set of events, and a plurality of rows forming cells with the one or more columns, each cell including one or more of the data items of the event attribute of a corresponding column. Based on a user selecting one or more of the cells, a list of options if displayed corresponding to the selection, and one or more commands are added to a search query that corresponds to the set of events, the one or more commands being based on at least an option that is selected from the list of options and the event attribute for each of the one or more of the data items of each of the selected one or more cells.

SPLITTING OF A JOIN OPERATION TO ALLOW PARALLELIZATION
20180004810 · 2018-01-04 ·

A system and method for processing a database query is described. In response to detection that a database query involves a star or snowflake join operation, a join operator in a preliminary query plan can be split into a build operator and a probe operator. The probe operator can be placed in a final query plan in the same place as the join operator in the preliminary query plan, while the build operator can be placed beneath the probe operator in the final query plan, between an exchange operator and the exchange operator's child from the preliminary query plan.

Performing geospatial-function join using implied interval join

Disclosed herein are systems and methods for performing a geospatial-function join using an implied interval join. In an embodiment, a database platform receives a query that includes a geospatial-function join, which applies a geospatial-function predicate to a first geography data object of a first relation and a second geography data object of a second relation. The database platform processes the first and second relations through an interval join that applies an interval-join predicate that is implied by the geospatial-function predicate. The database platform obtains query results at least in part by implementing a filter that applies the geospatial-function predicate to an output of the interval join, and outputs the query results.

Cache-aware system and method for identifying matching portions of two sets of data in a multiprocessor system

A system and method matches data from a first set of data with that of an other set of data in a manner based on the size of a cache.

Join elimination enhancement for real world temporal applications

A database system receives a query and determines that the query includes an inner join between a parent table and a child table. The database system determines that the following relationships exists between the parent table and the child table: referential integrity (“RI”) between a primary key attribute (pk) in the parent table and a foreign key attribute (fk) in the child table and a temporal relationship constraint (“TRC”) between a period attribute in the parent table and a TRC-attribute in the child table. The database system determines that the query satisfies non-temporal join elimination conditions and temporal join elimination conditions and that the query contains no other qualification conditions on the parent table's period attribute and eliminates the inner join when planning execution of the query.

Data fetch engine
11709836 · 2023-07-25 · ·

A method, apparatus, system, and computer program code for retrieving data records. A set of static configuration objects is provided, including: a set of resources that describe available data items, and a set of views that express a serialized transformation of resources objects into a response. In response to receiving a data request, a computer system generates a data fetch execution plan from the set of resources and the set of views. The data fetch execution plan is generated using an executor adapted to a particular data store and set of performance requirements. The computer system retrieves the data records according to the data fetch execution plan.

Dynamic-Ledger-Enabled Edge-Device Query Processing
20230222413 · 2023-07-13 ·

A method for processing a query for data stored in a distributed database includes receiving, at an edge device, the query for data stored in the distributed database from a query device. The method includes causing, by the edge device, the query to be stored on a dynamic ledger maintained by the distributed database. The method includes detecting, by the edge device, that summary data has been stored on the dynamic ledger. The method includes generating, by the edge device, an approximate response to the query based on the summary data stored on the dynamic ledger. The method includes transmitting, to the query device, the approximate response.

ENHANCING DATABASE QUERY PROCESSING
20230222124 · 2023-07-13 ·

A system, program product, and method for enhancing automatic multidimensional query processing. The method includes executing a database query including semi-joining a plurality of dimension tables with a fact table. The method also includes identifying for extraction one or more data values from each dimension table of the plurality of dimension tables. The data values from each dimension table of the plurality of dimension tables are associated with a respective record identification (RID), thereby defining one or more RIDs. The method further includes generating a plurality of RID lists. Each RID list of the plurality of RID lists includes a collection of the one or more RIDs for the respective dimension table. The method also includes merging the plurality of RID lists, sorting, subject to the merging, the plurality of RIDs as a function of data location, and fetching the data values from the fact table.

PRUNER SELECTOR

A data pre-processing architecture may include an interface and a pruning logic configured to receive, via the interface, at least one filter value from a query processor; use the at least one filter value to scan rows or columns of a data table stored in a memory; generate a selection indicator identifying a set of rows or columns of the data table where the at least one filter value resides; and provide to the query processor a filtered output based on the selection indicator.