Atscale, Inc.

Rouzbeh Safaie

Sarah Gerweck

Joseph Barefoot

Trystan R Leftwich

Daryl Odnert

Matthew Baird

Patrick J Toole

Daniel J Dosch

Gaurav Nitin Shetti

A preferred aggregate store for a multidimensional database receives and stores intermediate data generated as part of a larger query for avoiding repetitive or redundant data retrievals incurring costly data paths. Aggregates include intermediate tables and sets of data, often generated from a join of two or more distinct data tables, combined for generating a query result. In the event an aggregate is called for, certain storage locations may be preferable to others due to network distance, fees for storage and processing, as in the case of cloud storage, or write accessibility. Designation of a preferred aggregate store ensures that aggregates called for by the query processing are stored in a beneficial location for cost and efficiency.

Preferred storage of aggregate data items

A data query and retrieval system receives a query request and identifies a plurality of data warehouses, or stores, where data needed to satisfy the query is stored. Data items, or fields, called for by the query request are grouped into sets based on fields stored at the same data warehouse. Individual data connections are generated for each data warehouse accessed, and a database view defined for the fields available at each respective data warehouse. The individual views are invoked in a single query statement by a query processor for accessing the respective data warehouses via the corresponding database view. In this manner, a query operator or user need not define multiple query expressions or perform separate queries for accessing data fields or dimensions residing at different data warehouses.

Distributed queries through dynamic views

A query syntax analysis and postprocessing system and method receives a query request specifying values of a data type directed to a database without native support for the queried data type. A query engine or process for receiving a query request defined by a query syntax traverses the query request for a specification of an unsupported value or expression. In a large, distributed database environment, the query request may implicate multiple physical data stores, each having specific formats and recognized syntax. Values of unsupported or non-native types, or expressions that evaluate to an unsupported or non-native type, are identified and replaced with an expression that is recognized by the legacy database.

Query intake for legacy databases

A query engine or compute engine receiving a query request identifies a plurality of data sources for satisfying a query request, and determines, from among multiple data sources, one or more fields likely to incur substantial computational demands in processing the query request. Pre-positioning aggregation logic moves the determined fields one data source to another data source for positioning the moved fields to a single data source from which the query result will be computed.

Growing community of inventors

San Francisco, CA, United States of America

Rouzbeh Safaie