Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
1998-05-06
2001-02-13
Ho, Ruay Lian (Department: 2771)
Data processing: database and file management or data structures
Database design
Data structure types
C707S793000, C707S793000
Reexamination Certificate
active
06189004
ABSTRACT:
COPYRIGHT NOTICE
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by any one of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
THE FIELD OF THE INVENTION
This invention relates to the field of databases. In particular, the invention relates to creating databases, and loading and accessing data in the databases.
BACKGROUND OF THE INVENTION
Many different types of databases have been developed. On line transaction processing 3.- Ups (OLTP) databases are examples of typical databases used today. OLTP databases are concerned with the transaction oriented processing of data. On line transaction processing is the process by which data is entered and retrieved from these databases. In these transaction-oriented databases, every transaction is guaranteed. Thus, at a very low level, the OLTP databases are very good at determining whether any specific transaction has occurred.
Another type of database is a data warehouse or datamart. A datamart transforms the raw data from the OLTP databases. The transformation supports queries at a much higher level than the OLTP atomic transaction queries. A data warehouse or a datamart typically provides not only the structure for storing the data extracted from the OLTP databases, but also query analysis and publication tools.
The advantage of datamarts is that users can quickly access data that is important to their business decision making. To meet this goal, datamarts should have the following characteristics. First, datamarts should be consistent in that they give the same results for the same search. The datamart should also be consistent in the use of terms to describe fields in the datamart. For example, “sales” has a specific definition, that when fetched from a database, provides a consistent answer. Datamarts should also be able to separate and combine every possible measure in the business. Many of these issues are discussed in the following book, Ralph Kimball,
The Data Warehouse Toolkit,
John Whiley and Sons, Inc., New York, N.Y. (1996).
Multi-dimensional datamarts are one kind of datamart. Multi-dimensional datamarts rely on a dimension modeling technique to define the schema for the datamart. Dimension modeling involves visualizing the data in the datamart as a multi-dimension data space (e.g., image the data as a cube). Each dimension of that space corresponds to a different way of looking at the data. Each point in the space, defined by the dimensions, contains measurements for a particular combination of dimensions. For example, a three dimensional cube might have product, customer, and territory dimensions. Any point in that cube, defined by those three dimensions, will represent data that relates those three dimensions.
The data in the datamart is organized according to a schema. In a dimensional datamart, the data is typically organized as a star schema. At the center of a standard star schema is a fact table that contains measure data. Radiating outward from the fact table, like the points of a star, are multiple dimension tables. Dimension tables contain attribute data, such as the names of customers and territories. The fact table is connected, or joined, to each of the dimension tables, but the dimension tables are connected only to the fact table. This schema differs from that of many conventional relational databases where many tables are joined. The advantage of such a schema is that it supports a top down business approach to the definition of the schema.
Present datamarts have a number of drawbacks that are now discussed. First, datamarts are typically difficult to build and maintain. This is because of the requirements that they be consistent and flexible. A related drawback of present day datamarts is that they do not allow the consultants of the datamart to make changes to the schema simply and easily. Because datamarts support very high level queries about the business processes in the business, they require a great deal of consistency in the use of data from the OLTP systems. Additionally, the datamarts need to be very flexible to address changes in the types of high level queries supported. Changing typical datamarts require the changing of hundreds, or potentially thousands, of lines of SQL code. For example, if a fact column is added to a fact table, the change propagates throughout the datamart. These changes are typically implemented by hand, a very time consuming and error prone process. As a result of the hand coding involved, it is quite possible to construct the database in an arbitrary fashion that does not conform to good rules for constructing datamarts. Thus, well-formed datamarts may not result.
Thus an improved data warehousing technology is desired.
A SUMMARY OF THE INVENTION
One embodiment of the invention includes a method for automatically defining a query interface for a datamart. The datamart includes fact and dimension tables. The method comprises accessing a schema description and a query interface description for the datamart. The schema description specifies a schema, which in turn, defines the relationships between the fact tables and dimension tables of the datamart. The query interface description specifies the fields, related to the schema description, that can be used in a query and the way in which results are to be presented to the user. The fields correspond to columns and rows in the fact tables. The schema description is used to create a first set of commands to create and populate the fact and dimension tables. Additionally, a second set of commands to create the query interface is created. Some commands of the first set of commands are executed causing the creation and population of the tables. Some commands of the second set of commands are executed causing the creation of a user interface. A query is generated using the user interface. The query is sent to the system for processing. The results of the query are presented to the user according the second set of commands.
Although many details have been included in the description and the figures, the invention is defined by the scope of the claims. Only limitations found in those claims apply to the invention.
REFERENCES:
patent: 5386556 (1995-01-01), Hedin et al.
patent: 5550971 (1996-08-01), Brunner et al.
patent: 5659724 (1997-08-01), Borgida et al.
patent: 5675785 (1997-10-01), Hall et al.
patent: 5806060 (1998-09-01), Borgida et al.
patent: 5995958 (1999-11-01), Xu
Kimball, R., “The Data Warehouse Toolkit”, (1996) John-Wiley & Sons, Inc., 388 pages (includes CD ROM).
Chawathe, S. et al., “Change Detection in Hierarchically Structured Information”,SIGMOD Record,vol. 25, No. 2, Jun. 1996, pp. 493-504.
Chawathe, S. et al., “Meaningful Change Detection in Structured Data”, Proceedings of the 1997 ACM SIGMOD International Conference, ACM Press, 1997, pp. 26-37.
Labio, W. et al., “Efficient Snapshot Differential Algorithms for Data Warehousing”, Department of Computer Science, Stanford University, (1996), pp. 1-13.
Wiener, J. et al., “A System Prototype for Warehouse View Maintenance”,The Workshop on Materialized Views,pp. 26-33, Montreal, Canada, Jun. 1996.
Kawaguchi, A. et al., “Concurrency Control Theory for Deferred Materialized Views”, Database Theory—ICDT '97, Proceedings of the 6th International Conference, Delphi, Greece, Jan. 1997, pp. 306-320.
Zhuge, Y. et al., “Consistency Algorithms for Multi-Source Warehouse View Maintenance”,Distributed and Parallel Databases,vol. 6, pp. 7-40 (1998), Kluwer Academic Publishers.
Zhuge, Y. et al., “View Maintenance in a Warehousing Environment”,SIGMOD Record,vol. 24, No. 2, Jun. 1995, pp. 316-327.
Widom, J., “Research Problems in Data Warehousing”, Proc. of 4th Int'l Conference on Information and Knowledge Management (CIKM), Nov. 1995, 6 pages.
Yang, J. et al., “Maintaining Temporal Views Over Non-Historical Information Sources For Data
Litvak Emile
McCaskey John P.
Rassen Jeremy A.
Rauer Allon
shelat abhi a.
E. Piphany, Inc.
Ho Ruay Lian
Wilson Sonsoni Goodrich & Rosati
LandOfFree
Method and apparatus for creating a datamart and for... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method and apparatus for creating a datamart and for..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and apparatus for creating a datamart and for... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2585385