Roger Bolsius - Round Rock TX, US Raghuram Venkatasubramanian - Cupertino CA, US Ling Ni - Milpitas CA, US Donko Donjerkovic - Redwood City CA, US Saugata Chowdhury - Sunnyvale CA, US
Assignee:
Oracle International Corporation - Redwood Shores CA
International Classification:
G06F 17/30
US Classification:
707765, 707769
Abstract:
A business intelligence (BI) server and repository are described which support a set of customized and/or calculated data members. In accordance with an embodiment, the BI server maintains a connection to a plurality of data sources which may store a set of dimension members. The data source can be relational, file storage based, multidimensional and other types. In accordance with an embodiment, the BI server can accept queries from the user that contain calculated members as a parameter. The calculated member is defined by an expression including multiple dimension members and one or more arithmetic operators. The BI server can parse and validate the query and rewrite the query for the data source. After the query is rewritten and optimized, it is executed against the data source and a set of results is received.
Systems And Methods For Providing Value Hierarchies, Ragged Hierarchies And Skip-Level Hierarchies In A Business Intelligence Server
Roger Bolsius - Round Rock TX, US Raghuram Venkatasubramanian - Cupertino CA, US Ling Ni - Milpitas CA, US Donko Donjerkovic - Redwood City CA, US Saugata Chowdhury - Sunnyvale CA, US
Assignee:
ORACLE INTERNATIONAL CORPORATION - Redwood Shores CA
International Classification:
G06F 17/30
US Classification:
707714, 707769, 707E17017
Abstract:
A business intelligence (BI) server and repository are described which support a set of hierarchical relationships among the data. The BI server receives user input specifying a set of parent-child or other ancestral relationship among a set of data in a data source. The BI server generates a set of SQL queries and executes the queries to pre-populate a set of tables which specify the parent child relationships among the data in the data source. One such table is a parent-child relationship closure table that defines the inter-member relationships among the data members. Once the tables are populated, the BI server uses the closure tables to answer queries that require knowledge of the ancestral relationships among data.
Systems And Methods For Providing Multilingual Support For Data Used With A Business Intelligence Server
Roger Bolsius - Round Rock TX, US Raghuram Venkatasubramanian - Cupertino CA, US Ling Ni - Milpitas CA, US Donko Donjerkovic - Redwood City CA, US Saugata Chowdhury - Sunnyvale CA, US
Assignee:
ORACLE INTERNATIONAL CORPORATION - Redwood Shores CA
International Classification:
G06F 17/30
US Classification:
707714, 707E17017
Abstract:
A business intelligence (BI) server is described that supports data and schemas stored in multiple languages. The BI server implements a lookup table and lookup function that allows users to work with queries in different languages. When the user logs in, a session object is created for the user, which maintains the state information. A session variable specifies the language currently being used by the user. The BI server can inspect this session variable to determine the language of the user and perform the lookup translations as necessary. For example, if the language used by the session is different from the language of the base table storing the necessary information, the BI server can perform a translation by invoking a lookup function. The execution of the lookup can include performing a join operation of the base table with the lookup table to yield a translated value requested by the query.
- Sunnyvale CA, US Ambareesh Sreekumaran Nair Jayakumari - Cupertino CA, US Prateek Gaur - San Jose CA, US Donko Donjerkovic - San Mateo CA, US
International Classification:
G06F 16/2455 G06F 16/27 G06F 16/22 G06F 16/248
Abstract:
Querying a distributed database including a table sharded into shards distributed to database instances includes receiving a data-query that includes an aggregation clause on a first column and a grouping clause on a second column; obtaining and outputting results data. Obtaining the results data includes receiving, by a query coordinator, intermediate results data; and combining, by the query coordinator, the intermediate results to obtain the results data. Receiving the intermediate results data includes receiving, from a first database instance, first aggregation values indicating, on a per-group basis in accordance with the grouping clause, a respective aggregation value of distinct values of the first column in accordance with the aggregation clause, and receiving, from a second database instance, second aggregation values indicating, on a per-group basis in accordance with the grouping clause, a respective aggregation value of distinct values of the first column in accordance with the aggregation clause.
- San Jose CA, US Siva Singaram - San Jose CA, US Vishwas Sharma - Foster City CA, US Donko Donjerkovic - San Mateo CA, US Archit Bansal - Cupertino CA, US Rakesh Kothari - San Jose CA, US Sanchit Gupta - Sunnyvale CA, US
International Classification:
G06F 16/2458 G06F 16/22 G06F 16/248
Abstract:
Operating a low-latency data access and analysis system using domain-specific chronometry may include obtaining, in the low-latency data access and analysis system, data expressing usage intent with respect to the low-latency data access and analysis system, in response to obtaining the data expressing usage intent, obtaining ontological data for a chronometric object in the low-latency data access and analysis system indicated by the data expressing usage intent, identifying a chronometry dataset from a plurality of chronometry datasets, wherein the plurality of chronometry datasets includes a domain-specific chronometry dataset and a canonical chronometry dataset, obtaining results data in accordance with the chronometry dataset and the chronometric object, generating output data representing the results data in accordance with the chronometry dataset, and outputting the output data for presentation via a user interface.
- Sunnyvale CA, US Siva Singaram - San Jose CA, US Vishwas Sharma - Foster City CA, US Donko Donjerkovic - San Mateo CA, US Archit Bansal - Cupertino CA, US Rakesh Kothari - San Jose CA, US Sanchit Gupta - Sunnyvale CA, US
International Classification:
G06F 16/22
Abstract:
Operating a low-latency database analysis system using domain-specific chronometry may include obtaining chronometry configuration data including chronometric instance data describing an instance of a chronometric unit of a domain-specific chronometry dataset that describes an era, such that the chronometry configuration data includes respective chronometric instance data describing each instance of the first chronometric unit of the domain-specific chronometry dataset for the era of the domain-specific chronometry dataset, generating, in the low-latency database analysis system, a domain-specific chronometry dataset in accordance with the chronometry configuration data, such that the domain-specific chronometry dataset describes a chronometric unit such that a temporal location expressed with reference to the chronometric unit and indicative of an epoch value differs from a temporal location indicative of the epoch value and expressed in accordance with a canonical chronometry, and storing the domain-specific chronometry dataset in the low-latency database analysis system.
- Sunnyvale CA, US Siva Singaram - San Jose CA, US Vishwas Sharma - Foster City CA, US Donko Donjerkovic - San Mateo CA, US Archit Bansal - Cupertino CA, US Rakesh Kothari - San Jose CA, US Sanchit Gupta - Sunnyvale CA, US
International Classification:
G06F 16/2458 G06F 16/22 G06F 16/248 H04L 9/32
Abstract:
Operating a low-latency database analysis system using domain-specific chronometry may include obtaining, in the low-latency database analysis system, data expressing a usage intent with respect to the low-latency database analysis system, in response to obtaining the data expressing the usage intent, obtaining ontological data for a chronometric object in the low-latency database analysis system indicated by the data expressing the usage intent, identifying a chronometry dataset from a plurality of chronometry datasets, wherein the plurality of chronometry datasets includes a domain-specific chronometry dataset and a canonical chronometry dataset, obtaining results data in accordance with the chronometry dataset and the chronometric object, generating output data representing the results data in accordance with the chronometry dataset, and outputting the output data for presentation via a user interface.
Youtube
#Introduction to Relational Databases | #DBMS...
Introduction to Relational Databases | #DBMS |#Datamining |#Bigdata |#...