U.S. patent application number 10/153164 was filed with the patent office on 2003-01-23 for stand-alone cartridge style data aggregation server and method of and system for managing multi-dimensional databases using the same.
Invention is credited to Bakalash, Reuven, Caspi, Joseph, Shaked, Guy.
Application Number | 20030018642 10/153164 |
Document ID | / |
Family ID | 23450443 |
Filed Date | 2003-01-23 |
United States Patent
Application |
20030018642 |
Kind Code |
A1 |
Bakalash, Reuven ; et
al. |
January 23, 2003 |
Stand-alone cartridge style data aggregation server and method of
and system for managing multi-dimensional databases using the
same
Abstract
Improved method of and apparatus for aggregating data elements
in multidimensional databases (MDDB). In the preferred embodiment,
the apparatus is realized in the form of a high-performance
stand-alone (i.e. external) aggregation server which can be
plugged-into conventional MOLAP systems to achieve significant
improments in system performance. In accordance with the principles
of the present invention, the stand-alone aggregation server
contains a scalable MDDB and a high-performance aggregation engine
that are integrated into the modular architecture of the
aggregation server. The stand-alone aggregation server of the
present invention can uniformly distribute data elements among a
plurality of processors, for balanced loading and processing, and
therefore is highly scalable. The stand-alone aggregation server of
the present invention can be used to realize (i) an improved MDDB
for supporting on-line analytical processing (OLAP) operations,
(ii) an improved Internet URL Directory for supporting on-line
information searching operations by Web-enabled client machines, as
well as (iii) diverse types of MDDB-based systems for supporting
real-time control of processes in response to complex states of
information reflected in the MDDB.
Inventors: |
Bakalash, Reuven; (Shdema,
IL) ; Shaked, Guy; (Beer Sheva, IL) ; Caspi,
Joseph; (Herzlyia, IL) |
Correspondence
Address: |
Thomas J. Perkowski, Esq., P.C.
Soundview Plaza
1266 East Main Street
Stamford
CT
06902
US
|
Family ID: |
23450443 |
Appl. No.: |
10/153164 |
Filed: |
May 21, 2002 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10153164 |
May 21, 2002 |
|
|
|
09514611 |
Feb 28, 2000 |
|
|
|
6434544 |
|
|
|
|
09514611 |
Feb 28, 2000 |
|
|
|
09368241 |
Aug 4, 1999 |
|
|
|
6408292 |
|
|
|
|
Current U.S.
Class: |
1/1 ; 707/999.01;
707/E17.005; 707/E17.058 |
Current CPC
Class: |
G06F 16/24556 20190101;
G06F 16/283 20190101; Y10S 707/99933 20130101; Y10S 707/99932
20130101; Y10S 707/99943 20130101 |
Class at
Publication: |
707/10 |
International
Class: |
G06F 007/00 |
Claims
What is claimed is:
1. A stand-alone data aggregation server comprising an aggregation
engine that is integrated with a multidimensional database (MDDB),
to provide a cartridge-style plug-in accelerator which can
communicate with virtually any conventional OLAP server.
2. A stand-alone data aggregration server whose computational tasks
are restricted to data aggregation, leaving all other OLAP
functions to the MOLAP serverm and therefore complementing OLAP
server's functionality.
3. A stand-alone aggregation server carries out an improved method
of data aggregation within the MDDB which enables the dimensions of
the MDDB to be scaled up to large numbers and large atomic (i.e.
base) data sets to be handled within the MDDB.
4. A stand-alone aggregration server, wherein the aggregation
engine supports high-performance aggregation (i.e. data roll-up)
processes to maximize query performance of large data volumes, and
to reduce the time of partial aggregations that degrades the query
response.
5. A stand-alone, external scalable aggregation server, wherein its
integrated data aggregation (i.e. roll-up) engine speeds up the
aggregation process by orders of magnitude, enabling larger
database analysis by lowering the aggregation times.
6. A stand-alone scalable aggregation server for use in OLAP
operations, wherein the scalability of the aggregation server
enables (i) the speed of the aggregation process carried out
therewithin to be substantially increased by distributing the
computationally intensive tasks associated with data aggregation
among multiple processors, and (ii) the large data sets contained
within the MDDB of the aggregation server to be subdivided among
multiple processors thus allowing the size of atomic (i.e. basic)
data sets within the MDDB to be substantially increased.
7. A stand-alone scalable aggregation server, which provides for
uniform load balancing among processors for high efficiency and
best performance, and linear scalability for extending the limits
by adding processors.
8. A stand-alone, external scalable aggregation server, which is
suitable for MOLAP as well as for ROLAP system architectures.
9. A stand-alone scalable aggregation server, wherein an MDDB and
aggregation engine are integrated and the aggregation engine
carries out a high-performance aggregation algorithm and novel
storing and searching methods within the MDDB.
10. A stand-alone scalable aggregation server which can be
supported on single-processor (i.e. sequential or serial) computing
platforms, as well as on multiprocessor (i.e. parallel) computing
platforms.
11. A stand-alone scalable aggregation server which can be used as
a complementary aggregation plug-in to existing MOLAP and ROLAP
databases.
12. A stand-alone scalable aggregation server which carries out an
novel rollup (i.e. down-up) and spread down (i.e. top-down)
aggregation algorithms.
13. A stand-alone scalable aggregation server which includes an
integrated MDDB and aggregation engine which carries out full
pre-aggregation and/or "on-the-fly" aggregation processes within
the MDDB.
14. A stand-alone scalable aggregation server which is capable of
supporting MDDB having a multi-hierarchy dimensionality.
15. A method of aggregating multidimensional data of atomic data
sets originating from a RDBMS Data Warehouse.
16. A method of aggregating multidimensional data of atomic data
sets originating from other sources, such as external ASCII files,
MOLAP server, or other end user applications.
17. A stand-alone scalable data aggregation server which can
communicate with any MOLAP server via standard ODBC, OLE DB or DLL
interface, on a completely transparent manner with respect to the
(client) user, without any time delays in queries, equivalent to
storage in MOLAP server's cache.
18. A cartridge-style (stand-alone) scalable data aggregation
engine which dramatically expands the boundaries of MOLAP into the
large-scale applications including Banking, Insurance, Retail and
Promotion Analysis.
19. A cartridge-style (stand-alone) scalable data aggregation
engine which dramatically expands the boundaries of high-volatility
type ROLAP applications such as, for example, the precalculation of
data to maximize query performance.
20. A generic plug-in cartridge-type data aggregation component,
suitable for all MOLAP systems of different vendors, dramatically
reducing their aggregation burdens.
21. A high performance cartridge-type data aggregration server
which, having standardized interfaces, can be plugged-into the OLAP
system of virtually any user or vendor.
22. A cartridge-style (stand-alone) scalable data aggregation
engine which has the capacity to convert long batch-type data
aggregations into interactive sessions.
Description
RELATED CASE
[0001] This is a Continuation-in-part of: copending application
Ser. No. 09/368,241 entitled "Method Of And System For Managing
Multi-Dimensional Databases Using Modular-Arithmetic Based Address
Data Mapping Processes" filed Aug. 4, 1999; said Application being
commonly owned by HyperRoll, Limited, and incorporated herein by
reference in its entirety.
BACKGROUND OF THE INVENTION
[0002] 1. Field of Invention
[0003] The present invention relates to a method of and system for
aggregating data elements in a multi-dimensional database (MDDB)
supported upon a computing platform and also to provide an improved
method of and system for managing data elements within a MDDB
during on-line analytical processing (OLAP) operations.
[0004] 2. Brief Description of the State of the Art
[0005] The ability to act quickly and decisively in today's
increasingly competitive marketplace is critical to the success of
organizations. The volume of information that is available to
corporations is rapidly increasing and frequently overwhelming.
Those organizations that will effectively and efficiently manage
these tremendous volumes of data, and use the information to make
business decisions, will realize a significant competitive
advantage in the marketplace.
[0006] Data warehousing, the creation of an enterprise-wide data
store, is the first step towards managing these volumes of data.
The Data Warehouse is becoming an integral part of many information
delivery systems because it provides a single, central location
where a reconciled version of data extracted from a wide variety of
operational systems is stored. Over the last few years,
improvements in price, performance, scalability, and robustness of
open computing systems have made data warehousing a central
component of Information Technology CIT strategies. Details on
methods of data integration and constructing data warehouses can be
found in the white paper entitled "Data Integration: The Warehouse
Foundation" by Louis Rollleigh and Joe Thomas, published at
http://www.acxiom.com/whitep- apers/wp-11.asp.
[0007] Building a Data Warehouse has its own special challenges
(e.g. using common data model, common business dictionary, etc.)
and is a complex endeavor. However, just having a Data Warehouse
does not provide organizations with the often-heralded business
benefits of data warehousing. To complete the supply chain from
transactional systems to decision maker, organizations need to
deliver systems that allow knowledge workers to make strategic and
tactical decisions based on the information stored in these
warehouses. These decision support systems are referred to as
On-Line Analytical Processing (OLAP) systems. OLAP systems allow
knowledge workers to intuitively, quickly, and flexibly manipulate
operational data using familiar business terms, in order to provide
analytical insight into a particular problem or line of inquiry.
For example, by using an OLAP system, decision makers can "slice
and dice" information along a customer (or business) dimension, and
view business metrics by product and through time. Reports can be
defined from multiple perspectives that provide a high-level or
detailed view of the performance of any aspect of the business.
Decision makers can navigate throughout their database by drilling
down on a report to view elements at finer levels of detail, or by
pivoting to view reports from different perspectives. To enable
such full-functioned business analyses, OLAP systems need to (1)
support sophisticated analyses, (2) scale to large numbers of
dimensions, and (3) support analyses against large atomic data
sets. These three key requirements are discussed further below.
Decision makers use key performance metrics to evaluate the
operations within their domain, and OLAP systems need to be capable
of delivering these metrics in a user-customizable format. These
metrics may be obtained from the transactional databases
precalculated and stored in the database, or generated on demand
during the query process. Commonly used metrics include:
[0008] (1) Multidimensional Ratios (e.g. Percent to Total)
[0009] "Show me the contribution to weekly sales and category
profit made by all items sold in the Northwest stores between July
1 and July 14."
[0010] (2) Comparisons (e.g. Actual vs. Plan, This Period vs. Last
Period)
[0011] "Show me the sales to plan percentage variation for this
year and compare it to that of the previous year to identify
planning discrepancies."
[0012] (3) Ranking and Statistical Profiles (e.g. Top N/Bottom N,
70/30, Quartiles) "Show me sales, profit and average call volume
per day for my 20 most profitable salespeople, who are in the top
30% of the worldwide sales."
[0013] (4) Custom Consolidations
[0014] "Show me an abbreviated income statement by quarter for the
last two quarters for my Western Region operations."
[0015] Knowledge workers analyze data from a number of different
business perspectives or dimensions. As used hereinafter, a
dimension is any element or hierarchical combination of elements in
a data model that can be displayed orthogonally with respect to
other combinations of elements in the data model. For example, if a
report lists sales by week, promotion, store, and department, then
the report would be a slice of data taken from a four-dimensional
data model.
[0016] Target marketing and market segmentation applications
involve extracting highly qualified result sets from large volumes
of data. For example, a direct marketing organization might want to
generate a targeted mailing list based on dozens of
characteristics, including purchase frequency, size of the last
purchase, past buying trends, customer location, age of customer,
and gender of customer. These applications rapidly increase the
dimensionality requirements for analysis.
[0017] The number of dimensions in OLAP systems range from a few
orthogonal dimensions to hundreds of orthogonal dimensions.
Orthogonal dimensions in an exemplary OLAP application might
include Geography, Time, and Products.
[0018] Atomic data refers to the lowest level of data granularity
required for effective decision making. In the case of a retail
merchandising manager, "atomic data" may refer to information by
store, by day, and by item. For a banker, atomic data may be
information by account, by transaction, and by branch. Most
organizations implementing OLAP systems find themselves needing
systems that can scale to tens, hundreds, and even thousands of
gigabytes of atomic information.
[0019] As OLAP systems become more pervasive and are used by the
majority of the enterprise, more data over longer time frames will
be included in the data store (i.e. data warehouse), and the size
of the database will increase by at least an order of magnitude.
Thus, OLAP systems need to be able to scale from present to
near-future volumes of data.
[0020] In general, OLAP systems need to (1) support the complex
analysis requirements of decision-makers, (2) analyze the data from
a number of different perspectives (i.e. business dimensions), and
(3) support complex analyses against large input (atomic-level)
data sets from a Data Warehouse maintained by the organization
using a relational database management system (RDBMS).
[0021] Vendors of OLAP systems classify OLAP Systems as either
Relational OLAP (ROLAP) or Multidimensional OLAP (MOLAP) based on
the underlying architecture thereof. Thus, there are two basic
architectures for On-Line Analytical Processing systems: The ROLAP
Architecture, and the MOLAP architecture.
[0022] Overview of the Relational OLAP (ROLAP) System
Architecture
[0023] The Relational OLAP (ROLAP) system accesses data stored in a
Data Warehouse to provide OLAP analyses. The premise of ROLAP is
that OLAP capabilities are best provided directly against the
relational database, i.e. the Data Warehouse.
[0024] The ROLAP architecture was invented to enable direct access
of data from Data Warehouses, and therefore support optimization
techniques to meet batch window requirements and provide fast
response times. Typically, these optimization techniques include
application-level table partitioning, preaggregate inferencing,
denormalization support, and the joining of multiple fact
tables.
[0025] A typical prior art ROLAP system has a three-tier or layer
client/server architecture. The "database layer" utilizes
relational databases for data storage, access, and retrieval
processes. The "application logic layer" is the ROLAP engine which
executes the multidimensional reports from multiple users. The
ROLAP engine integrates with a variety of "presentation layers,"
through which users perform OLAP analyses.
[0026] After the data model for the data warehouse is defined, data
from on-line transaction-processing (OLTP) systems is loaded into
the relational database management system (RDBMS). If required by
the data model, database routines are run to pre-aggregate the data
within the RDBMS. Indices are then created to optimize query access
times. End users submit multidimensional analyses to the ROLAP
engine, which then dynamically transforms the requests into SQL
execution plans. The SQL execution plans are submitted to the
relational database for processing, the relational query results
are cross-tabulated, and a multidimensional result data set is
returned to the end user. ROLAP is a fully dynamic architecture
capable of utilizing precalculated results when they are available,
or dynamically generating results from atomic information when
necessary.
[0027] Overview of MOLAP System Architecture
[0028] Multidimensional OLAP (MOLAP) systems utilize a proprietary
multidimensional database (MDDB) to provide OLAP analyses. The main
premise of this architecture is that data must be stored
multidimensionally to be accessed and viewed
multidimensionally.
[0029] As shown in FIG. 1B, prior art MOLAP systems have an
Aggregation, Access and Retrieval module which is responsible for
all data storage, access, and retrieval processes, including data
aggregration (i.e. preaggregation) in the MDDB. As shown in FIG.
1B, the base data loader is fed with base data, in the most
detailed level, from the Data Warehouse, into the Multi-Dimensional
Data Base (MDDB). On top of the base data, layers of aggregated
data are built-up by the Aggregation program, which is part of the
Aggregation, Access and Retrieval module. As indicated in this
figure, the application logic module is responsible for the
execution of all OLAP requests/queries (e.g. ratios, ranks,
forecasts, exception scanning, and slicing and dicing) of data
within the MDDB. The presentation module integrates with the
application logic module and provides an interface, through which
the end users view and request OLAP analyses on their client
machines which may be web-enabled through the infrastructure of the
Internet. The client/server architecture of a MOLAP system allows
multiple users to access the same multidimensional database
(MDDB).
[0030] Information (i.e. basic data) from a variety of operational
systems within an enterprise, comprising the Data Warehouse, is
loaded into a prior art multidimensional database (MDDB) through a
series of batch routines. The Express.TM. server by the Oracle
Corporation is exemplary of a popular server which can be used to
carry out the data loading process in prior art MOLAP systems. As
shown in FIG. 2B an exemplary 3-D MDDB is schematically depicted,
showing geography, time and products as the "dimensions" of the
database. The multidimensional data of the MDDB is organized in an
array structure, as shown in FIG. 2C. Physically, the Express.TM.
server stores data in pages (or records) of an information file.
Pages contain 512, or 2048, or 4096 bytes of data, depending on the
platform and release of the Express.TM. server. In order to look up
the physical record address from the database file recorded on a
disk or other mass storage device, the Express.TM. server generates
a data structure referred to as a "Page Allocation Table (PAT)". As
shown in FIG. 2D, the PAT tells the Express.TM. server the physical
record number that contains the page of data. Typically, the PAT is
organized in pages. The simplest way to access a data element in
the MDDB is by calculating the "offset" using the additions and
multiplications expressed by a simple formula:
Offset=Months+Product*(#of_Months)+City*(#of_Months*#of_Products)
[0031] During an OLAP session, the response time of a
multidimensional query on a prior art MDDB depends on how many
cells in the MDDB have to be added "on the fly". As the number of
dimensions in the MDDB increases linearly, the number of the cells
in the MDDB increases exponentially. However, it is known that the
majority of multidimensional queries deal with summarized high
level data. Thus, as shown in FIGS. 3A and 3B, once the atomic data
(i.e. "basic data") has been loaded into the MDDB, the general
approach is to perform a series of calculations in batch in order
to aggregate (i.e. pre-aggregate) the data elements along the
orthogonal dimensions of the MDDB and fill the array structures
thereof. For example, revenue figures for all retail stores in a
particular state (i.e. New York) would be added together to fill
the state level cells in the MDDB. After the array structure in the
database has been filled, integer-based indices are created and
hashing algorithms are used to improve query access times.
Pre-aggregation of dimension D0 is always performed along the
cross-section of the MDDB along the D0 dimension.
[0032] As shown in FIG. 3C2, the primarily loaded data in the MDDB
is organized at its lowest dimensional hierarchy. As shown in FIGS.
3C1 and 3C3, the results of the pre-aggregations are stored in the
neighboring parts of the MDDB.
[0033] As shown in FIG. 3C2, along the TIME dimension, weeks are
the aggregation results of days, months are the aggregation results
of weeks, and quarters are the aggregation results of months. While
not shown in the figures, along the GEOGRAPHY dimension, states are
the aggregation results of cities, countries are the aggregation
results of states, and continents are the aggregation results of
countries. By pre-aggregating (i.e. consolidating or compiling) all
logical subtotals and totals along all dimensions of the MDDB, it
is possible to carry out real-time MOLAP operations using a
multidimensional database (MDDB) containing both basic (i.e.
atomic) and pre-aggregated data. Once this compilation process has
been completed, the MDDB is ready for use. Users request OLAP
reports by submitting queries through the OLAP Application
interface (e.g. using web-enabled client machines), and the
application logic layer responds to the submitted queries by
retrieving the stored data from the MDDB for display on the client
machine.
[0034] Typically, in MDDB systems, the aggregated data is very
sparse, tending to explode as the number of dimension grows and
dramatically slowing down the retrieval process (as described in
the report entitled "Database Explosion: The OLAP Report",
http://www.olapreport.com/Database- Explosion.htm, incorporated
herein by reference). Quick and on line retrieval of queried data
is critical in delivering on-line response for OLAP queries.
Therefore, the data structure of the MDDB, and methods of its
storing, indexing and handling are dictated mainly by the need of
fast retrieval of massive and sparse data.
[0035] Different solutions for this problem are disclosed in the
following US patents, each of which is incorporated herein by
reference in its entirety:
[0036] U.S. Pat. No. 5,822,751 "Efficient Multidimensional Data
Aggregation Operator Implementation"
[0037] U.S. Pat. No. 5,805,885 "Method And System For Aggregation
Objects"
[0038] U.S. Pat. No. 5,781,896 "Method And System For Efficiently
Performing Database Table Aggregation Using An Aggregation
Index"
[0039] U.S. Pat. No. 5,745,764 "Method And System For Aggregation
Objects"
[0040] In all the prior art OLAP servers, the process of storing,
indexing and handling MDDB utilize complex data structures to
largely improve the retrieval speed, as part of the querying
process, at the cost of slowing down the storing and aggregation.
The query-bounded structure, that must support fast retrieval of
queries in a restricting environment of high sparcity and
multi-hierarchies, is not the optimal one for fast aggregation.
[0041] In addition to the aggregation process, the Aggregation,
Access and Retrieval module is responsible for all data storage,
retrieval and access processes. The Logic module is responsible for
the execution of OLAP queries. The Presentation module
intermediates between the user and the logic module and provides an
interface through which the end users view and request OLAP
analyses. The client/server architecture allows multiple users to
simultaneously access the multidimensional database.
[0042] In summary, general system requirements of OLAP systems
include: (1) supporting sophisticated analysis, (2) scaling to
large number of dimensions, and (3) supporting analysis against
large atomic data sets.
[0043] MOLAP system architecture is capable of providing
analytically sophisticated reports and analysis functionality.
However, requirements (2) and (3) fundamentally limit MOLAP's
capability, because to be effective and to meet end-user
requirements, MOLAP databases need a high degree of
aggregation.
[0044] By contrast, the ROLAP system architecture allows the
construction of systems requiring a low degree of aggregation, but
such systems are significantly slower than systems based on MOLAP
system architecure principles. The resulting long aggregation times
of ROLAP systems impose severe limitations on its volumes and
dimensional capabilities.
[0045] The graphs plotted in FIG. 5 clearly indicate the
computational demands that are created when searching an MDDB
during an OLAP session, where answers to queries are presented to
the MOLAP system, and answers thereto are solicited often under
real-time constraints. However, prior art MOLAP systems have
limited capabilities to dynamically create data aggregations or to
calculate business metrics that have not been precalculated and
stored in the MDDB.
[0046] The large volumes of data and the high dimensionality of
certain market segmentation applications are orders of magnitude
beyond the limits of current multidimensional databases.
[0047] ROLAP is capable of higher data volumes. However, the ROLAP
architecture, despite its high volume and dimensionality
superiority, suffers from several significant drawbacks as compared
to MOLAP:
[0048] Full aggregation of large data volumes are very time
consuming, otherwise, partial aggregation severely degrades the
query response.
[0049] It has a slower query response
[0050] It requires developers and end users to know SQL
[0051] SQL is less capable of the sophisticated analytical
functionality necessary for OLAP
[0052] ROLAP provides limited application functionality
[0053] Thus, improved techniques for data aggregation within MOLAP
systems would appear to allow the number of dimensions of and the
size of atomic (i.e. basic) data sets in the MDDB to be
significantly increased, and thus increase the usage of the MOLAP
system architecture.
[0054] Also, improved techniques for data aggregation within ROLAP
systems would appear to allow for maximized query performance on
large data volumes, and reduce the time of partial aggregations
that degrades query response, and thus generally benefit ROLAP
system architectures.
[0055] Thus, there is a great need in the art for an improved way
of and means for aggregating data elements within a
multi-dimensional database (MDDB), while avoiding the shortcomings
and drawbacks of prior art systems and methodologies.
SUMMARY AND OBJECTS OF PRESENT INVENTION
[0056] Accordingly, it is a further object of the present invention
to provide a n improved method of and system for managing data
elements within a multidimensional database (MDDB) using a novel
stand-alone (i.e. external) data aggregation server, achieving a
significant increase in system performance (e.g. deceased
access/search time) using a stand-alone scalable data aggregation
server.
[0057] Another object of the present invention is to provide such
system, wherein the stand-alone aggregation server includes an
aggregation engine that is integrated with an MDDB, to provide a
cartridge-style plug-in accelerator which can communicate with
virtually any conventional OLAP server.
[0058] Another object of the present invention is to provide such a
stand-alone data aggregration server whose computational tasks are
restricted to data aggregation, leaving all other OLAP functions to
the MOLAP server and therefore complementing OLAP server's
functionality.
[0059] Another object of the present invention is to provide such a
system, wherein the stand-alone aggregation server carries out an
improved method of data aggregation within the MDDB which enables
the dimensions of the MDDB to be scaled up to large numbers and
large atomic (i.e. base) data sets to be handled within the
MDDB.
[0060] Another object of the present invention is to provide such a
stand-alone aggregration server, wherein the aggregation engine
supports high-performance aggregation (i.e. data roll-up) processes
to maximize query performance of large data volumes, and to reduce
the time of partial aggregations that degrades the query
response.
[0061] Another object of the present invention is to provide such a
stand-alone, external scalable aggregation server, wherein its
integrated data aggregation (i.e. roll-up) engine speeds up the
aggregation process by orders of magnitude, enabling larger
database analysis by lowering the aggregation times.
[0062] Another object of the present invention is to provide such a
novel standalone scalable aggregation server for use in OLAP
operations, wherein the scalability of the aggregation server
enables (i) the speed of the aggregation process carried out
therewithin to be substantially increased by distributing the
computationally intensive tasks associated with data aggregation
among multiple processors, and (ii) the large data sets contained
within the MDDB of the aggregation server to be subdivided among
multiple processors thus allowing the size of atomic (i.e. basic)
data sets within the MDDB to be substantially increased.
[0063] Another object of the present invention is to provide such a
novel standalone scalable aggregation server, which provides for
uniform load balancing among processors for high efficiency and
best performance, and linear scalability for extending the limits
by adding processors.
[0064] Another object of the present invention is to provide a
stand-alone, external scalable aggregation server, which is
suitable for MOLAP as well as for ROLAP system architectures.
[0065] Another object of the present invention is to provide a
novel stand-alone scalable aggregation server, wherein an MDDB and
aggregation engine are integrated and the aggregation engine
carries out a high-performance aggregation algorithm and novel
storing and searching methods within the MDDB.
[0066] Another object of the present invention is to provide a
novel stand-alone scalable aggregation server which can be
supported on single-processor (i.e. sequential or serial) computing
platforms, as well as on multi-processor (i.e. parallel) computing
platforms.
[0067] Another object of the present invention is to provide a
novel stand-alone scalable aggregation server which can be used as
a complementary aggregation plug-in to existing MOLAP and ROLAP
databases.
[0068] Another object of the present invention is to provide a
novel stand-alone scalable aggregation server which carries out an
novel rollup (i.e. down-up) and spread down (i.e. top-down)
aggregation algorithms.
[0069] Another object of the present invention is to provide a
novel stand-alone scalable aggregation server which includes an
integrated MDDB and aggregation engine which carries out full
pre-aggregation and/or "on-the-fly" aggregation processes within
the MDDB.
[0070] Another object of the present invention is to provide such a
novel standalone scalable aggregation server which is capable of
supporting MDDB having a multi-hierarchy dimensionality.
[0071] Another object of the present invention is to provide a
novel method of aggregating multidimensional data of atomic data
sets originating from a RDBMS Data Warehouse.
[0072] Another object of the present invention is to provide a
novel method of aggregating multidimensional data of atomic data
sets originating from other sources, such as external ASCII files,
MOLAP server, or other end user applications.
[0073] Another object of the present invention is to provide a
novel stand-alone scalable data aggregation server which can
communicate with any MOLAP server via standard ODBC, OLE DB or DLL
interface, in a completely transparent manner with respect to the
(client) user, without any time delays in queries, equivalent to
storage in MOLAP server's cache.
[0074] Another object of the present invention is to provide a
novel "cartridge-style" (stand-alone) scalable data aggregation
engine which dramatically expands the boundaries of MOLAP into
large-scale applications including Banking, Insurance, Retail and
Promotion Analysis.
[0075] Another object of the present invention is to provide a
novel "cartridge-style" (stand-alone) scalable data aggregation
engine which dramatically expands the boundaries of high-volatility
type ROLAP applications such as, for example, the precalculation of
data to maximize query performance.
[0076] Another object of the present invention is to provide a
generic plug-in cartridge-type data aggregation component, suitable
for all MOLAP systems of different vendors, dramatically reducing
their aggregation burdens.
[0077] Another object of the present invention is to provide a
novel high performance cartridge-type data aggregration server
which, having standardized interfaces, can be plugged-into the OLAP
system of virtually any user or vendor.
[0078] Another object of the present invention is to provide a
novel "cartridge-style" (stand-alone) scalable data aggregation
engine which has the capacity to convert long batch-type data
aggregations into interactive sessions.
[0079] These and other object of the present invention will become
apparent hereinafter and in the claims to Invention set forth
herein.
BRIEF DESCRIPTION OF THE DRAWINGS
[0080] In order to more fully appreciate the objects of the present
invention, the following Detailed Description of the Illustrative
Embodiments should be read in conjunction with the accompanying
Drawings, wherein:
[0081] FIG. 1A is a schematic representation of an exemplary prior
art relations on-line analytical processing (ROLAP) system
comprising a three-tier or layer client/server architecture,
wherein the first tier has a database layer utilizing relational
databases (RDBMS) for data storage, access, and retrieval
processes, the second tier has an application logic layer (i.e. the
ROLAP engine) for executing the multidimensional reports from
multiple users, and the third tier integrates the ROLAP engine with
a variety of presentation layers, through which users perform OLAP
analyses;
[0082] FIG. 1B is a schematic representation of a generalized
embodiment of a prior art multidimensional on-line analytical
processing (MOLAP) system comprising a base data loader for
receiving atomic (i.e. base) data from a Data Warehouse realized by
a RDBMS, an OLAP multidimensional database (MDDB), an aggregation,
access and retrival module, application logic module an d
presentation module associated with a conventional OLAP sever (e.g.
Oracle's Express Server) for supporting on-line transactional
processing (OLTP) operations on the MDDB, to service database
queries and requests from a plurality of OLAP client machines
typically accessing the system from an information network (e.g.
the Internet);
[0083] FIG. 2A is a schematic representation of the Data Warehouse
shown in the prior art system of FIG. 1B comprising numerous data
tables (e.g. T1, T2, . . . Tn) and data field links, and the OLAP
multidimensional database shown of FIG. 1B, comprising a
conventional page allocation table (PAT) with pointers pointing to
the physical storage of variables in an information storage
device;
[0084] FIG. 2B is a schematic representation of an exemplary
three-dimensional MDDB and organized as a 3-dimensional Cartesian
cube and used in the prior art system of FIG. 2A, wherein the first
dimension of the MDDB is representative of geography (e.g. cities,
states, countries, continents), the second dimension of the MDDB is
representative of time (e.g. days, weeks, months, years), the third
dimension of the MDDB is representative of products (e.g. all
products, by manufacturer), and the basic data element is a set of
variables which are addressed by 3-dimensional coordinate
values;
[0085] FIG. 2C is a schematic representation of a prior art array
structure associated with an exemplary three-dimensional MDDB,
arranged according to a dimensional hierarchy;
[0086] FIG. 2D is a schematic representation of a prior art page
allocation table for an exemplary three-dimensional MDDB, arranged
according to pages of data element addresses;
[0087] FIG. 3A is a schematic representation of a prior art MOLAP
system, illustrating the process of periodically storing raw data
in the RDBMS Data Warehouse thereof, serially loading of basic data
from the Data Warehouse to the MDDB, and the process of serially
pre-aggregating (or pre-compiling) the data in the MDDB along the
entire dimensional hierarchy thereof;
[0088] FIG. 3B is a schematic representation illustrating that the
Cartesian addresses listed in a prior art page allocation table
(PAT) point to where physical storage of data elements (i.e.
variables) occurs in the information recording media (e.g. storage
volumes) associated with the MDDB, during the loading of basic data
into the MDDB as well as during data preaggregation processes
carried out therewithin;
[0089] FIG. 3C1 is a schematic representation of an exemplary
three-dimensional database used in a conventional MOLAP system of
the prior art, showing that each data element contained therein is
physically stored at a location in the recording media of the
system which is specified by the dimensions (and subdimensions
within the dimensional hierarchy) of the data variables which are
assigned integer-based coordinates in the MDDB, and also that data
elements associated with the basic data loaded into the MDDB are
assigned lower integer coordinates in MDDB Space than
pre-aggregated data elements contained therewithin;
[0090] FIG. 3C2 is a schematic representation illustrating that a
conventional hierarchy of the dimension of "time" typically
contains the subdimensions "days, weeks, months, quarters, etc." of
the prior art;
[0091] FIG. 3C3 is a schematic representation showing how data
elements having higher subdimensions of time in the MDDB of the
prior art are typically assigned increased integer addresses along
the time dimension thereof;
[0092] FIG. 4 is a schematic representation illustrating that, for
very large prior art MDDBs, very large page allocation tables
(PATs) are required to represent the address locations of the data
elements contained therein, and thus there is a need to employ
address data paging techniques between the DRAM (e.g. program
memory) and mass storage devices (e.g. recording discs or RAIDs)
available on the serial computing platform used to implement such
prior art MOLAP systems;
[0093] FIG. 5 is a graphical representation showing how search time
in a conventional (i.e. prior art) MDDB increases in proportion to
the amount of preaggregation of data therewithin;
[0094] FIG. 6A is a schematic representation of a generalized
embodiment of a multidimensional on-line analytical processing
(MOLAP) system of the present invention comprising a Data Warehouse
realized as a relational database, a stand-alone Aggregration
Server of the present invention having an integrated aggregation
engine and MDDB, and an OLAP server supporting a plurality of OLAP
clients, wherein the stand-alone Aggregation Server performs
aggregation functions (e.g. summation of numbers, as well as other
mathematical operations, such as multiplication, subtraction,
division etc.) and multidimensional data storage functions;
[0095] FIG. 6B is a schematic block diagram of the stand-alone
Aggregation Server of the illustrative embodiment shown in FIG. 6A,
showing its primary components, namely, a base data interface (e.g.
OLDB, OLE-DB, ODBC, SQL, API, JDBC, etc.) for receiving RDBMS flat
files lists and other files from the Data Warehouse (RDBMS), a base
data loader for receiving base data from the base data interface,
configuration manager for managing the operation of the base data
interface and base data loader, an aggregation engine for receiving
base data from the base loader, a multi-dimensional database
(MDDB), a MDDB handler for handling the movement of base data and
aggregation data between the aggregation engine and the MDDB, an
input analyzer, an aggregation client interface (e.g. OLDB, OLE-DB,
ODBC, SQL, API, JDBC, etc.) for receiving requests from OLAP client
machines and receiving data files from the input analyzer for
transfer to requesting OLAP clients, and a configuration manager
for managing the operation of the input analyzer and the
aggregation client interface;
[0096] FIG. 6C is a schematic representation of the software
modules comprising the aggregation engine and MDDB handler of the
stand-alone Aggregation Server of the illustrative embodiment of
the present invention, showing a base data list structure being
supplied to a hierarchy analysis and reorder module, the output
thereof being transferred to an aggregation management module, the
output thereof being transferred to a storage module via a storage
management module, and a Query Directed Roll-up (QDR) aggregation
management module being provided for receiving database (DB)
requests from OLAP client machines and managing the operation of
the aggregation and storage management modules of the present
invention;
[0097] FIG. 6D is a flow chart representation of the primary
operations carried out by the (DB) request serving mechanism within
the QDR aggregation management module shown in FIG. 6C;
[0098] FIG. 7A is a schematic representation of a separate-platform
type implementation of the stand-alone Aggregation Server of the
illustrative embodiment of FIG. 6B and a conventional OLAP server
supporting a plurality of client machines, wherein base data from a
Data Warehouse is shown being received by the aggregation server,
realized on a first hardware/software platform (i.e. Platform A)
and the stand-alone Aggregation Server is shown serving the
conventional OLAP server, realized on a second hardware/software
platform (i.e. Platform B), as well as serving data aggregation
requirements of other clients supporting diverse applications such
as spreadsheet, GUI front end, and applications;
[0099] FIG. 7B is a schematic representation of a shared-platform
type implementation of the stand-alone Aggregation Server of the
illustrative embodiment of FIG. 6B and a conventional OLAP server
supporting a plurality of client machines, wherein base data from a
Data Warehouse is shown being received by the stand-alone
Aggregation Server, realized on a common hardware/software platform
and the aggregation server is shown serving the conventional OLAP
server, realized on the same common hardware/software platform, as
well as serving data aggregation requirements of other clients
supporting diverse applications such as spreadsheet, GUI front end,
and applications;
[0100] FIG. 8A is a data table setting forth information
representative of performance benchmarks obtained by the
shared-platform type implementation of the stand-alone Aggregation
Server of the illustrative embodiment serving the conventional OLAP
server (i.e. Oracle EXPRESS Server) shown in FIG. 7B, wherein the
common hardware/software platform is realized using a Pentium H 450
Mhz, 1 GB RAM, 18 GB Disk, running the Microsoft NT operating
system (OS):
[0101] FIG. 9A is a schematic representation of the first stage in
the method of segmented aggregation according to the principles of
the present invention, showing initial aggregration along the 1st
dimension;
[0102] FIG. 9B is a schematic representation of the next stage in
the method of segmented aggregation according to the principles of
the present invention, showing that any segment along dimension 1,
such as the shown slice, can be separately aggregated along the
remaining dimensions, 2 and 3, and that in general, for an N
dimensional system, the second stage involves aggregation in N-1
dimensions. The principle of segementation can be applied on the
first stage as well, however, only a large enough data will justify
such a sliced procedure in the first dimension. Actually, it is
possible to consider each segment as an N-1 cube, enabling
recursive computation.
[0103] FIG. 9C1 is a schematic representation of the Query Directed
Roll-up (QDR) aggregation method/procedure of the present
invention, showing data aggregation starting from existing basic
data or previously aggregated data in the first dimension (D1), and
such aggregated data being utilized as a basis for QDR aggregation
along the second dimension (D2);
[0104] FIG. 9C2 is a schematic representation of the Query Directed
Roll-up (QDR) aggregation method/procedure of the present
invention, showing initial data aggregation starting from existing
previously aggregated data in the second third (D3), and continuing
along the third dimension (D3), and thereafter continuing
aggregation along the second dimension (D2);
[0105] FIG. 10A is a schematic representation of the
"slice-storage" method of storing sparse data in the disk storage
devices of the MDDB of FIG. 6B in accordance with the principles of
the present invention, based on an ascending-ordered index along
aggregation direction, enabling fast retrieval of data;
[0106] FIG. 10B is a schematic representation of the data
organization of data files and the directory file used in the
storages of the MDDB of FIG. 6B, and the method of searching for a
queried data point therein using a simple binary search technique
due to the data files ascending order;
[0107] FIG. 11A is a schematic representation of three exemplary
multi-hierarchical data structures for storage of data within the
MDDB of FIG. 6B, having three levels of hierarchy, wherein the
first level representative of base data is composed of items A,B,F,
and G, the second level is composed of items C,E,H and I, and the
third level is composed of a single item D, which is common to all
three hierarchical structures;
[0108] FIG. 11B is a schematic representation of an optimized
multi-hierarchical data structure merged from all three hierarchies
of FIG. 11A, in accordance with the principles of the present
invention;
[0109] FIG. 12 is a schematic representation showing the levels of
operations performed by the stand-alone Aggregation Server of FIG.
6B, summarizing the different enabling components for carrying out
the method of segmented aggregation in accordance with the
principles of the present invention; and
[0110] FIG. 13 is a schematic representation of the stand-alone
Aggregation Server of the present invention shown as a component of
a central data warehouse, serving the data aggregation needs of URL
directory systems, Data Marts, RDBMSs, ROLAP systems and OLAP
systems alike.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS OF THE PRESENT
INVENTION
[0111] Referring now to FIGS. 6A through 13, the preferred
embodiments of the method and system of the present invention will
be now described in great detail hereinbelow, wherein like elements
in the Drawings shall be indicated by like reference numerals.
[0112] Through this invention disclosure, the term "aggregation"
and "preaggregation" shall be understood to mean the process of
summation of numbers, as well as other mathematical operations,
such as multiplication, subtraction, division etc.
[0113] In general, the stand-alone aggregation server and methods
of and apparatus for data aggregation of the present invention can
be employed in a wide range of applications, including MOLAP
systems, ROLAP systems, Internet URL-directory systems,
personalized on-line e-commerce shopping systems, Internet-based
systems requiring real-time control of packet routing and/or
switching, and the like.
[0114] For purposes of illustration, initial focus will be accorded
to improvements in MOLAP systems, in which knowledge workers are
enabled to intuitively, quickly, and flexibly manipulate
operational data within a MDDB using familiar business terms in
order to provide analytical insight into a business domain of
interest.
[0115] FIG. 6A illustrates a generalized embodiment of a
multidimensional online analytical processing (MOLAP) system of the
present invention comprising: a Data Warehouse realized as a
relational database; a stand-alone cartridge-style Aggregation
Server of the present invention having an integrated aggregation
engine and a MDDB; and an OLAP server communicating with the
Aggregation Server, and supporting a plurality of OLAP clients. In
accordance with the principles of the present invention, the
stand-alone Aggregation Server performs aggregation functions (e.g.
summation of numbers, as well as other mathematical operations,
such as multiplication, subtraction, division etc.) and
multi-dimensional data storage functions.
[0116] Departing from conventional practices, the principles of the
present invention teaches moving the aggregation engine and the
MDDB into a separate Aggregation Server having standardized
interfaces so that it can be plugged-into the OLAP system of
virtually any user or vendor. This dramatic move discontinues the
restricting dependency of aggregation from the analytical functions
of OLAP, and by applying novel and independent algorithms. The
stand-alone data aggregation server enables efficient organization
and handling of data, fast aggregation processing, and fast access
to and retrieval of any data element in the MDDB.
[0117] As will be described in greater detail hereinafter, the
Aggregation Server of the present invention can serve the data
aggregation requirements of other types of systems besides OLAP
systems such as, for example, URL directory management Data Marts,
RDBMS, or ROLAP.
[0118] The Aggregation Server of the present invention excels in
performing two distinct functions, namely: the aggregation of data
in the MDDB; and the handling of the resulting data base in the
MDDB, for "on demand" client use. In the case of serving an OLAP
system, the Aggregation Server of the present invention focuses on
performing these two functions in a high performance manner (i.e.
aggregating and storing base data, originated at the Data
Warehouse, in a multidimensional storage (MDDB), and providing the
results of this data aggregation process "on demand" to the
clients, such as the OLAP server, spreadsheet applications, the end
user applications. As such, the Aggregation Server of the present
invention frees each conventional OLAP server, with which it
interfaces, from the need of making data aggregations, and
therefore allows the conventional OLAP server to concentrate on the
primary functions of OLAP servers, namely: data analysis and
supporting a graphical interface with the user client.
[0119] FIG. 6B shows the primary components of the stand-alone
Aggregation Server of the illustrative embodiment, namely: a base
data interface (e.g. OLDB, OLE-DB, ODBC, SQL, API, JDBC, etc.) for
receiving RDBMS flat files lists and other files from the Data
Warehouse (RDBMS), a base data loader for receiving base data from
the base data interface, configuration manager for managing the
operation of the base data interface and base data loader, an
aggregation engine for receiving base data from the base loader, a
multi-dimensional database (MDDB); a MDDB handler, an input
analyzer, an aggregation client interface (e.g. OLDB, OLE-DB, ODBC,
SQL, API, JDBC, etc.) and a configuration manager for managing the
operation of the input analyzer and the aggregation client
interface.
[0120] During operation, the base data originates at data warehouse
or other sources, such as external ASCII files, MOLAP server, or
others. The Configuration Manager, in order to enable proper
communication with all possible sources and data structures,
configures two blocks, the Base Data Interface and Data Loader.
Their configuration is matched with different standards such as
OLDB, OLE-DB, ODBC, SQL, API, JDBC, etc.
[0121] As shown in FIG. 6B, the core of the data Aggregation Server
of the present invention comprises: a data Aggregation Engine; a
Multidimensional Data Handler; and a Multidimensional Data Storage.
The results of data aggregation are efficiently stored in a
multidimensional structure (MDDB) within the Multidimensional Data
Storage, by the Data Handler.
[0122] As shown in FIGS. 6A and 6B, the stand-alone Aggregation
Server of the present invention serves the MOLAP Server via
standard interfaces, such as OLDB, OLE-DB, ODBC, SQL, API, JDBC,
etc. Aggregation results required by the MOLAP server are supplied
on demand. Typically, the OLAP Server disintegrates the query, via
parsing process, into series of requests. Each such request,
specifying a n-dimensional coordinate, is presented to the
Aggregation Server for the coordinate's value. The Configuration
Manager sets the Aggregation Client Interface and Input Analyzer
for a proper communication protocol according to the client user.
The Input Analyzer converts the input format to make it suitable
for the MDDB Handler.
[0123] An object of the present invention is to make the transfer
of data completely transparent to the OLAP user, in a manner which
is equivalent to the storing of data in the MOLAP server's cache
and without any query delays. This requires that the stand-alone
Aggregation Server have exceptionally fast response
characteristics. This object is enabled by providing the unique
data structure and aggregation mechanism of the present
invention.
[0124] FIG. 6C shows the software modules comprising the
aggregation engine and MDDB handler components of the stand-alone
Aggregation Server of the illustrative embodiment. The base data
list, as it arrives from RDBMS or text files, has to be analyzed
and reordered to optimize hierarchy handling, according to the
unique method of the present invention, as described later with
reference to FIGS. 11A and 11B.
[0125] The function of the aggregation management module is to
administrate the aggregation process according to the method
illustrated in FIGS. 9A and 9B.
[0126] In accordance with the principles of the present invention,
data aggregation within the stand-alone Aggregation Server can be
carried out either as a complete pre-aggregation process, where the
base data is fully aggregated before commencing querying, or as a
query directed roll-up (QDR) process, where querying is allowed at
any stage of aggregation using the "on-the-fly" data aggregation
process of the present invention. The QDR process will be described
hereinafter in greater detail with reference to FIG. 9C. The
response to a request (i.e. a basic component of a client query),
by calling the Aggregation management module for "on-the-fly" data
aggregation, or for accessing pre-aggregated result data via the
Storage management module. The query/request serving mechanism of
the present invention within the QDR aggregation management module
is illustrated in the flow chart of FIG. 6D.
[0127] The function of the Storage management module is to handle
multidimensional data in the storage(s) module in a very efficient
way, according to the novel method of the present invention, which
will be described in detail hereinafter with reference to FIGS. 10A
and 10B.
[0128] The request serving mechanism shown in FIG. 6D is controlled
by the QDR aggregation management module. Requests are queued and
served one by one. If the required data is already pre-calculated,
then it is retrieved by the storage management module and returned
to the client. Otherwise, the required data is calculated
"on-the-fly" by the aggregation management module, and the result
moved out to the client, while simultaneously stored by the storage
management module, shown in FIG. 6C.
[0129] FIGS. 7A and 7B outline two different implementations of the
stand-alone (cartridge-style) Aggregation Server of the present
invention. In both implementations, the Aggregation Server supplies
aggregated MDDB results to a client.
[0130] FIG. 7A shows a separate-platform implementation of the
MOLAP system of the illustrative embodiment shown in FIG. 6A,
wherein the Aggregation Server of the present invention resides on
a separate hardware platform and OS system from that used to run
the OLAP server. In this type of implementation, it is even
possible to run the Aggregation Server and the OLAP Server on
different-type operating systems (e.g. NT, Unix, MAC OS).
[0131] FIG. 7B shows a common-platform implementation of the MOLAP
system of the illustrative embodiment shown in FIG. 6B, wherein the
Aggregation Server of the present invention shares the same
hardware platform and operating system (OS) that used to run the
client OLAP Server.
[0132] FIG. 8A shows a table setting forth the benchmark results of
an aggregation engine, implemented on a shared/common hardware
platform and OS, in accordance with the principles of the present
invention. The common platform and OS is realized using a Pentium
II 450 Mhz, IGB RAM, 18 GB Disk, running the Microsoft NT operating
system. The six (6) data sets shown in the table differ in number
of dimensions, number of hierarchies, measure of sparcity and data
size. A comparison with ORACLE Express, a major OLAP server, is
made. It is evident that the aggregation engine of the present
invention outperforms currently leading aggregation technology by
more than an order of magnitude.
[0133] The segmented data aggregation method of the present
invention is described in FIGS. 9A through 9C2. These figures
outline a simplified setting of three dimensions only; however, the
following analysis applies to any number of dimensions as well.
[0134] The data is being divided into autonomic segments to
minimize the amount of simultaneously handled data. The initial
aggregation is practiced on a single dimension only, while later on
the aggregation process involves all other dimensions.
[0135] At the first stage of the aggregation method, an aggregation
is performed along dimension 1. The first stage can be performed on
more than one dimension. As shown in FIG. 9A, the space of the base
data is expanded by the aggregation process.
[0136] In the next stage shown in FIG. 9B, any segment along
dimension 1, such as the shown slice, can be separately aggregated
along the remaining dimensions, 2 and 3. In general, for an N
dimensional system, the second stage involves aggregation in N-1
dimensions.
[0137] The principle of data segmentation can be applied on the
first stage as well. However, only a large enough data set will
justify such a sliced procedure in the first dimension. Actually,
it is possible to consider each segment as an N-1 cube, enabling
recursive computation.
[0138] It is imperative to get aggregation results of a specific
slice before the entire aggregation is completed, or alternatively,
to have the roll-up done in a particular sequence. This novel
feature of the aggregation method of the present invention is that
it allows the querying to begin, even before the regular
aggregation process is accomplished, and still having fast
response. Moreover, in relational OLAP and other systems requiring
only partial aggregations, the QDR process dramatically speeds up
the query response.
[0139] The QDR process is made feasible by the slice-oriented
roll-up method of the present invention. After aggregating the
first dimension(s), the multidimensional space is composed of
independent multidimensional cubes (slices). These cubes can be
processed in any arbitrary sequence.
[0140] Consequently the aggregation process of the present
invention can be monitored by means of files, shared memory
sockets, or queues to statically or dynamically set the roll-up
order.
[0141] In order to satisfy a single query coming from a client,
before the required aggregation result has been prepared, the QDR
process of the present invention involves performing a fast
on-the-fly aggregation (roll-up) involving only a thin slice of the
multidimensional data.
[0142] FIG. 9C1 shows a slice required for building-up a roll-up
result of the 2.sup.nd dimension. In case 1, as shown, the
aggregation starts from an existing data, either basic or
previously aggregated in the first dimension. This data is utilized
as a basis for QDR aggregation along the second dimension. In case
2, due to lack of previous data, a QDR involves an initial slice
aggregation along dimension 3, and thereafter aggregation along the
2.sup.nd dimension.
[0143] FIG. 9C2 shows two corresponding QDR cases for gaining
results in the 3 d dimension. Cases 1 and 2 differ in the amount of
initial aggregation required in 2.sup.nd dimension.
[0144] FIG. 10A illustrates the "Slice-Storage" method of storing
sparse data on storage disks. In general, this data storage method
is based on the principle that an ascending-ordered index along
aggregation direction, enables fast retrieval of data. FIG. 10A
illustrates a unit-wide slice of the multidimensional cube of data.
Since the data is sparse, only few non-NA data points exist. These
points are indexed as follows. The Data File consists of data
records, in which each n-1 dimensional slice is being stored, in a
separate record. These records have a varying length, according to
the amount of non-NA stored points. For each registered point in
the record, IND.sub.K stands for an index in a n-dimensional cube,
and Data stands for the value of a given point in the cube.
[0145] FIG. 10B illustrates a novel method for randomly searching
for a queried data point in the MDDB of FIG. 6B by using a novel
technique of organizing data files and the directory file used in
the storages of the MDDB, so that a simple binary search technique
can then be employed within the Aggregation Server of the prsent
invention. According to this method, a metafile termed DIR File,
keeps pointers to Data Files as well as additional parameters such
as the start and end addresses of data record (IND.sub.0,
IND.sub.n), its location within the Data File, record size (n),
file's physical address on disk (D_Path), and auxiliary information
on the record (Flags).
[0146] A search for a queried data point is then performed by an
access to the DIR file. The search along the file can be made using
a simple binary search due to file's ascending order. When the
record is found, it is then loaded into main memory to search for
the required point, characterized by its index IND.sub.k. The
attached Data field represents the queried value. In case the exact
index is not found, it means that the point is a NA.
[0147] FIGS. 11A and 11B illustrate a novel method for
pre-processing data such that multi-hierarchies in
multi-hierarchical structures are optimally merged.
[0148] In particular, FIG. 11A illustrates a novel method which the
stand-alone Aggregation Server employs for handling hierarchies.
According to the devised method, the inner order of hierarchies
within a dimension is optimized, to achieve efficient data handling
for summations and other mathematical formulas (termed in general
"Aggregation"). The order of hierarchy is defined externally. It is
brought from a data source to the stand-alone aggregation engine,
as a descriptor of data, before the data itself. In the
illustrative embodiment, the method assumes hierarchical relations
of the data, as shown in FIG. 11A. The way data items are ordered
in the memory space of the Aggregation Server, with regard to the
hierarchy, has a significant impact on its data handling
efficiency.
[0149] Notably, when using prior art techniques, multiple handling
of data elements, which occurs when a data element is accessed more
than once during aggregation process, has been hitherto unavoidable
when the main concern is to effectively handle the sparse data. The
data structures used in prior art data handling methods have been
designed for fast access to a non NA data. According to prior art
techniques, each access is associated with a timely search and
retrieval in the data structure. For the massive amount of data
typically accessed from a Data Warehouse in an OLAP application,
such multiple handling of data elements has significantly degraded
the efficiency of prior art data aggregation processes. When using
prior art data handling techniques, the data element D shown in
FIG. 11A must be accessed three times, causing poor aggregation
performance.
[0150] In accordance with the data handling method of the present
present, the data is being pre-ordered for a singular handling, as
opposed to multiple handling taught by prior art methods. According
to the present invention, elements of base data and their
aggregated results are contiguously stored in a way that each
element will be accessed only once. This particular order allows a
forward-only handling, never backward. Once a base data element is
stored, or aggregated result is generated and stored, it is never
to be retrieved again for further aggregation. As a result the
storage access is minimized. This way of singular handling greatly
elevates the aggregation efficiency of large data bases. An
efficient handling method as used in the present invention, is
shown in FIG. 7A. The data element D, as any other element, is
accessed and handled only once.
[0151] FIG. 11A shows an example of a multi-hierarchical database
structure having 3 hierarchies. As shown, the base data includes
the items A,B,F, and G., The second level is composed of items
C,E,H and I. The third level has a single item D, which is common
to all three hierarchical structures. In accordance with the method
of the present invention, a minimal computing path is always taken.
For example, according to the method of the present invention, item
D will be calculated as part of structure 1, requiring two
mathematical operations only, rather than as in structure 3, which
would need four mathematical operations. FIG. 11B depicts an
optimized structure merged from all three hierarchies.
[0152] FIG. 12 summarizes the different enabling components for
segmented aggregation. The minimized operations in handling
multi-hierarchies need analysis of the base data. It greatly
optimizes data handling and contribute to aggregation speed. Based
on this technology loading and indexing operations become very
efficient, minimizing memory and storage access, and speeding up
storing and retrieval operations. On top of all the enabling
technologies is the segmented aggregation technique, not just
outperforming by orders of magnitude the prior-art aggregation
algorithms, but also enabling the unique QDR which waves out the
need of waiting for full pre-aggregation.
[0153] FIG. 13 shows the stand-alone Aggregation Server of the
present invention as a component of a central data warehouse,
serving the data aggregation needs of URL directory systems, Data
Marts, RDBMSs, ROLAP systems and OLAP systems alike.
[0154] The reason for the central multidimensional database's rise
to corporate necessity is that it facilitates flexible,
high-performance access and analysis of large volumes of complex
and interrelated data.
[0155] A stand-alone specialized aggregation server, simultaneously
serving many different kinds of clients (e.g. data mart, OLAP, URL,
RDBMS), has the power of delivering an enterprise-wide aggregation
in a cost-effective way. This kind of server eliminates the roll-up
redundancy over the group of clients, delivering scalability and
flexibility.
[0156] Performance associated with central data warehouse is an
important consideration in the overall approach. Performance
includes aggregation times and query response.
[0157] Effective interactive query applications require near
real-time performance, measured in seconds. These application
performances translate directly into the aggregation
requirements.
[0158] In the prior art, in case of MOLAP, a full pre-aggregation
must be done before starting querying. In the present invention, in
contrast to prior art, the query directed roll-up (QDR) allows
instant querying, while the full preaggregation is done in the
background. In cases a full pre-aggregation is preferred, the
currently invented aggregation outperforms any prior art. For the
ROLAP and RDBMS clients, partial aggregations maximize query
performance. In both cases fast aggregation process is imperative.
The aggregation performance of the current invention is by orders
of magnitude higher than that of the prior art.
[0159] The stand-alone scalable aggregation server of the present
invention can be used in any MOLAP system environment for answering
questions about corporate performance in a particular market,
economic trends, consumer behaviors, weather conditions, population
trends, or the state of any physical, social, biological or other
system or phenomenon on which different types or categories of
information, organizable in accordance with a predetermined
dimensional hierarchy, are collected and stored within a RDBMS of
one sort or another. Regardless of the particular application
selected, the address data mapping processes of the present
invention will provide a quick and efficient way of managing a MDDB
and also enabling decision support capabilities utilizing the same
in diverse application environments.
[0160] Functional Advantages Gained by the Data Aggregation Server
of the Present Invention
[0161] The stand-alone "cartridge-style" plug-in features of the
data aggregation server of the present invention, provides freedom
in designing an optimized multidimensional data structure and
handling method for aggregation, provides freedom in designing a
generic aggregation server matching all OLAP vendors, and enables
enterprise-wide centralized aggregation.
[0162] The method of Segmented Aggregation employed in the
aggregation server of the present invention provides flexibility,
scalability, a condition for Query Directed Aggregation, and speed
improvement.
[0163] The method of Multidimensional data organization and
indexing employed in the aggregation server of the present
invention provides fast storage and retrieval, a condition for
Segmented Aggregation, improves the storing, handling, and
retrieval of data in a fast manner, and contributes to structural
flexibility to allow sliced aggregation and QDR. It also enables
the forwarding and single handling of data with improvements in
speed performance.
[0164] The method of Query Directed Aggregation (QDR) employed in
the aggregation server of the present invention minimizes the data
handling operations in multi-hierarchy data structures.
[0165] The method of Query Directed Aggregation (QDR) employed in
the aggregation server of the present invention eliminates the need
to wait for full aggregation to be completed, and provides build-up
aggregated data required for full aggregation.
[0166] It is understood that the System and Method of the
illustrative embodiments described hereinabove may be modified in a
variety of ways which will become readily apparent to those skilled
in the art of having the benefit of the novel teachings disclosed
herein. All such modifications and variations of the illustrative
embodiments thereof shall be deemed to be within the scope and
spirit of the present invention as defined by the claims to
Invention appended hereto.
* * * * *
References