Relational database management system having integrated non-relational multi-dimensional data store or aggregated data elements

Abstract

Improved method of and apparatus for joining and aggregating data elements integrated within a relational database management system (RDBMS) using a non-relational multi-dimensional data structure (MDD). The improved RDBMS system of the present invention can be used to realize achieving a significant increase in system performance (e.g. deceased access/search time), user flexibility and ease of use. The improved RDBMS system of the present invention can be used to realize an improved Data Warehouse for supporting on-line analytical processing (OLAP) operations or to realize an improved informational database system or the like.

1 - 34 . (canceled)  
     
     
         35 . A relational database management system (RDBMS) for servicing query statements through one or more client machines, said RDBMS comprising: 
 a RDBMS query interface adapted to receive query statements from said one or more client machines;    a query processing mechanism for processing each query statement received from said RDBMS query interface, and generating one or more query requests by disintegrating the query statement so that each said query request specifies a set of dimensions, and determining how to service query requests with data available to said RDBMS;    a query handling mechanism operably coupled to said RDBMS query interface;    a relational data store having relational tables for storing fact data, and a meta-data store for storing a dictionary containing dimension data;    a multi-dimensional database (MDDB) for storing aggregated fact data in a multi-dimensional data structure;    a data loading mechanism for loading said meta-data and said fact data into said MDDB;    an aggregation engine for calculating aggregated fact data from the fact data according to a multi-dimensional data aggregation process;    a data handling mechanism for storing aggregated fact data in said MDDB and retrieving aggregated fact data from said MDDB;    wherein said query handling mechanism (i) receives each query request, (ii) extracts a set of dimensions associated with said query request, (iii) uses said dimensions to retrieve aggregated fact data from said MDDB, and (iv) forwards retrieved aggregated fact data to said query processing mechanism for subsequent processing, if needed; and    wherein when said query processing mechanism determines that servicing of one or more query requests requires aggregated fact data stored in said MDDB, then said query processing mechanism automatically routes said one or more query requests to said MDDB so that aggregated fact data can be accessed from said MDDB and forwarded to said query processing mechanism for use in servicing the given query statement, in a manner transparent to said client machine.    
     
     
         36 . The RDBMS of  claim 35 , wherein after data loading operations, the fact data is initially aggregated along at least one of the dimensions extracted from said dictionary and aggregated fact data is stored in said MDDB, and wherein during query servicing operations, the fact data is aggregated on demand along additional dimensions extracted from said query request.  
     
     
         37 . The RDBMS of  claim 36 , which further comprises storing the aggregated fact data in said MDDB after said aggregated fact data has been aggregated along additional dimensions.  
     
     
         38 . The RDBMS of  claim 35 , wherein said multi-dimensional aggregation process further operates as follows: 
 (a) if the aggregated fact data required to service a given query request is already pre-calculated and stored within said MDDB, then the pre-aggregated fact data is retrieved by said data handling mechanism and returned to said client machine; and    (b) if the required fact data is not already pre-aggregated and stored within said MDDB, then the required aggregated fact data is calculated on demand by said aggregation engine, and the aggregated fact data result is automatically forwarded to said client machine.    
     
     
         39 . The RDBMS of  claim 35 , wherein said multi-dimensional data structure comprises a plurality of data storage cells, and wherein each said data storage cell is indexed with multiple dimensions and stores either base data values or aggregated fact data values.  
     
     
         40 . The RDBMS of  claim 35 , wherein during data loading operations, said data loading mechanism extracts dimension data from the dictionary in said meta-data store, and forwards the dimension data to said MDDB for configuration using said dimension data.  
     
     
         41 . The RDBMS of  claim 35 , wherein during aggregation operations, said data loading mechanism extracts fact data from said relational tables, and forwards the fact data to said MDDB; and wherein said aggregation engine calculates aggregated fact data from the fact data according to said multi-dimensional data aggregation process, and stores the aggregated fact data in said MDDB.  
     
     
         42 . The RDBMS of  claim 35 , wherein said query statement is an SQL-type query statement and each query request is an SQL-type query request.  
     
     
         43 . The RDBMS of  claim 35 , wherein said RDBMS query interface is implemented in a module within said RDBMS.  
     
     
         44 . The RDBMS of  claim 35 , wherein a user interacts with said client machine using a web-enabled browser to generate a natural language type query statement, and said natural language type query statement is communicated to said RDBMS query interface.