Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
1999-12-17
2003-03-11
Metjahic, Safet (Department: 2171)
Data processing: database and file management or data structures
Database design
Data structure types
Reexamination Certificate
active
06532470
ABSTRACT:
BACKGROUND OF THE INVENTION
1. The Field of the Invention
The present invention relates to database systems and more specifically, to manners of utilizing summary tables with a database system that does not otherwise support summary tables.
2. The Relevant Technology
A summary table, otherwise known as a materialized view, is a pre-computed and stored result of a query. A standard view is a derived relation defined in terms of base relations. A view defines a function mapped from a set of base tables to a derived table. This function is typically recomputed every time the view is referenced. A view becomes a materialized view when the tuples generated by the view are stored in a database. Index structures can be built on the materialized view. Consequently, database accesses to the materialized view can be much faster than recomputing the view. A materialized view or summary table is thus like a cache, essentially embodying a copy of selected data that can be accessed quickly.
The data stored in a database is generally accessed using a query formatted in the SQL language native to most existing database systems. It is a primary objective in designing database systems to be able to service queries with the least cost, that is, in the lowest amount of time. One manner of decreasing query response time is with the use of summary tables. It is often the case that certain data can be accessed more quickly by accessing one or more summary tables in which copies of the data have been stored. Summary tables are generally quite small relative to the entire database, and scanning a summary table is much more efficient than scanning multiple relations of a database. Thus, one technique for speeding up query servicing is to maintain a plurality of summary tables and to selectively direct queries to the appropriate summary table for which the query can be most rapidly serviced. It would be advantageous to employ summary tables directed to the various heterogeneous database systems in query optimization.
As a further complication to the employment of summary tables in multiple database systems (MDBS), some database systems do not support summary tables. In order to provide more efficient query servicing, it is desirable to utilize summary tables in such an environment.
Additionally, it is considered by the inventors to be advantageous in some instances to be able to support the summary tables locally within the respective databases of an MDBS, rather than within a centralized database management program. The benefits of so doing include better performance for a class of queries that involve computation on large amounts of data but that yields relatively smaller result sets; the possibility for using the remote source's replication utilities for maintaining the currency of the summary table; and the enablement of the remote database's applications to take advantage of the summary table.
It would be further advantageous if a single central program could be employed to support and manage summary tables on a plurality of heterogeneous database systems, including where necessary, on databases that do not natively support summary tables.
Accordingly, a need exists for a distributed database system that capitalizes on the use of summary tables. To best utilize such a system, the capability should be provided to centrally generate, maintain, and query the summary tables. The system preferably makes provisions for communicating with database systems that do not support summary tables. Such a distributed database system and its method of use are disclosed herein.
OBJECTS AND BRIEF SUMMARY OF THE INVENTION
The apparatus of the present invention has been developed in response to the present state of the art, and in particular, in response to the problems and needs in the art that have not yet been fully solved by currently available database management systems. Thus, it is an overall objective of the present invention to provide a distributed database apparatus, system, and article of manufacture that capitalizes on summary tables within a plurality of heterogeneous database tables.
The apparatus of the present invention has been developed in response to the present state of the art, and in particular, in response to the problems and needs in the art that have not yet been fully solved by currently available database management systems. Thus, it is an overall objective of the present invention to provide an apparatus, system, and article of manufacture for supporting summary tables within a database system that does not otherwise support summary tables.
To achieve the foregoing object, and in accordance with the invention as embodied and broadly described herein in the preferred embodiment, a central database management system, method, and article of manufacture are provided. The central database management system is preferably implemented with modules for execution by a processor. In one embodiment, the modules comprise a communication module configured to communicate with the database system and to initiate the generation of an unrecognized summary table corresponding to the database system. The modules preferably also comprise an identification module in communication with the communication module and configured to identify the unrecognized summary table as a summary table.
As used herein, unrecognized summary table is generally intended to mean a database table containing summary data that is not particularly recognized by the database system containing the data that is summarized by the summary table and/or hosting the summary table as being a summary table.
In one embodiment, the system of the present invention comprises a central database communications program (central program) in which the communication module and the identification module are located. The unrecognized summary table may be situated within the central program or may be located within the database system. Where the unrecognized summary table is generated within the central program, the database system may remain unaware of the existence of the unrecognized summary table.
The unrecognized summary table in one embodiment comprises summary data corresponding to a database of the database system and is recognized by the database system as a normal table and by the central program as a summary table.
The identification module may comprise a catalog within or in communication with the central program. In this embodiment, the central program is configured to list an alias of the unrecognized summary table within the catalog, and to list corresponding information within the catalog identifying the unrecognized summary table as a summary table.
In one embodiment, the central program also comprises a summary table creation module. Preferably, the summary table creation module is configured to initiate the generation of the unrecognized summary table within the database system. In so doing, the summary table creation module preferably transmits commands from the central program to the database system to instruct the database system to generate the unrecognized summary table. The commands may be, for instance, DDL commands. The DDL commands in one embodiment comprise a SQL command selecting entries from a table of the database system where a selected criterion is met.
The summary table creation module may be configured to receive from a user a summary table create command, and in response generate a SQL command and transmit the SQL command to the database system to instruct the database system to generate the unrecognized summary table. The summary table creation module may be further configured to assign the unrecognized summary table an alias and the central program may be configured to store the alias and information regarding the contents of the summary table within the catalog.
The system in one embodiment also comprises a query processing module. The query processing module is preferably configured to receive a query from a user and in response generate a query plan that directs SQL queries to the unrecognized summary table
Cochrane Roberta Jo
Kleewein James C.
Leung Ting Yu
Pirahesh Mir Hamid
Subramanina Narayana
Kunzler & Associates
Metjahic Safet
Nguyen Cam-Linh T.
LandOfFree
Support for summary tables in a database system that does... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Support for summary tables in a database system that does..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Support for summary tables in a database system that does... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3034602