VALUE-INSTANCE-CONNECTIVITY COMPUTER-IMPLEMENTED DATABASE

• US 20080319939A1
• Filed: 08/15/2008
• Published: 12/25/2008
• Est. Priority Date: 07/08/1998
• Status: Abandoned Application

• Current Assignee: Stephan A. Tarin
• Original Assignee: Stephan A. Tarin
• Inventors: TARIN, Stephan A.
• Application Number:
  US12/192,434
• Publication Number:
  US 20080319939A1
• Time in Patent Office: Days
• US Class Current: 707/1
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/283 Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A computer-implemented database and method providing an efficient, ordered reduced space representation of multi-dimensional data. The data values for each attribute are stored in a manner that provides an advantage in, for example, space usage and/or speed of access, such as in condensed form and/or sort order. Instances of each data value for an attribute are identified by instance elements, each of which is associated with one data value. Connectivity information is provided for each instance element that uniquely associates each instance element with a specific instance of a data value for another attribute.

Claims

1. A method of retrieving a record from a compressed database:

a. retrieving information regarding the number of occurrences of a given value from the database, the database having been compressed by storing information regarding distinct values of an attribute and information regarding the number of occurrences of distinct values;

b. determining an instance element based on information regarding the number of occurrences of the given value;

c. determining a connectivity element based on the instance element; and

d. determining a record from the connectivity element.

2. The method of claim 1, wherein the step of retrieving the information regarding the number of occurrences of the given value comprises analyzing a cardinality store.

3. The method of claim 1, wherein the step of determining an instance element information regarding the number of occurrences of the given value comprises analyzing an instance store.

4. The method of claim 1, wherein the step of determining the connectivity element comprises analyzing a connectivity store.

5. The method of claim 1, wherein the step of determining a record comprises analyzing a value store.

6. The method of claim 1, wherein the retrieving of the record is caused by an Structured Query Language (SQL) query.

7. The method of claim 1, wherein the SQL query is a SELECT query.