Efficient schema for storing multi-value attributes in a directory service backing store

• US 6,865,576 B1
• Filed: 05/21/1999
• Issued: 03/08/2005
• Est. Priority Date: 05/21/1999
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Murthy, Chetan Ram, Mancisidor, Rodolfo Augusto, Gong, Shia-San, Shi, Shaw-Ben
• Primary Examiner(s): An, Meng-Al T.
• Assistant Examiner(s): Vo, Lilian
• Application Number:
  US09/316,754
• Time in Patent Office: 2,118 Days
• Field of Search: 707/103, 707/10, 707/3, 707/102, 707/101, 707/2, 709/100
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A database schema for storing application data in a relational database backing store of a directory service. The application data has at least some entries with multiple value attributes. According to the invention, the application data is profiled to determine how it may be optimally stored in the backing store. Preferably, single entries having single value attributes are stored in a merged attribute table, while entries having multiple value attributes are stored in per attribute tables. According to the optimization, a majority of the attributes are single valued and are stored in the merged table, and the per attribute tables thus store a relatively smaller number of exceptions. This database schema enhances processing of conventional directory service queries into the backing store.

Claims

1. A method for storing data that has at least some entries with multiple value attributes, comprising the steps of:

profiling the data to determine whether the data should be stored in an attribute table or, alternatively, in a merged table and an overflow table; and

storing the data optimally based on the profiling step;

wherein a majority of the data is stored in the merged table and a set of additional values for the multiple value attributes are stored in the overflow table.

2. The method as described in claim 1 wherein the entries with single value attributes are stored in the merged table.

3. The method as described in claim 1 wherein the entries with multiple value attributes are stored in the overflow table.

4. The method as described in claim 1 wherein the overflow table is an attribute table.

5. The method as described in claim 1 wherein the profiling step parses the data to identify entries with single value attributes.

6. The method as described in claim 1 wherein the profiling step parses the data to identify given operations that are performed on the data once stored.

7. The method as described in claim 1 wherein the data is stored in a relational database backing store.