Database system, method of managing database, and computer-readable storage medium

• US 9,104,711 B2
• Filed: 05/28/2009
• Issued: 08/11/2015
• Est. Priority Date: 05/30/2008
• Status: Active Grant

• Current Assignee: NEC Corporation
• Original Assignee: NEC Corporation
• Inventors: Kashiwagi, Takehiko, Kamimura, Junpei
• Primary Examiner(s): Jalil, Neveen Abel
• Assistant Examiner(s): TORGRIMSON, TYLER J
• Application Number:
  US12/995,165
• Publication Number:
  US 20110087697A1
• Time in Patent Office: 2,266 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2228 Indexing structures
• CPC Class Codes: G06F 16/2255 Hash tables

Abstract

Disclosed is a database system capable of effectively updating data in a database at a high speed. The database system includes: a storage unit that stores a database including an entity data group and at least one identifier table having only a plurality of fixed-length data; and a data processing unit that receives a query and performs data processing on the database on the basis of the received query. The identifier table has a plurality of data identifiers that uniquely indicates the plurality of entity data as the fixed-length data.

Claims

1. A database system comprising:

a storage unit that stores a database including an entity data group containing a plurality of entity data, a plurality of identifier tables each having only fixed-length data and each having, as the fixed-length data, a reference identifier and a data identifier in each tuple of a plurality of tuples that eliminates overlap with other identifier tables, and a reference table having the reference identifiers in each tuple, wherein the data identifier uniquely indicates one of the plurality of entity data, and the reference identifiers in each tuple of the reference table uniquely indicate the data identifiers in the different identifier tables,

wherein each reference identifier of the set of reference identifiers in the tuple of the reference table uniquely identifies one of the data identifiers stored in one of the identifier tables; and

a transaction processing unit that receives a query and performs transaction processing on the database on the basis of the received query using the reference table and the identifier tables and transmits a result of the transaction processing back to a device that initiated the query,

wherein the transaction processing unit;

converts a data record into a reference record including reference identifiers;

adds the reference record as one tuple to the reference table;

determines whether all of the reference identifiers included in the added tuple have already been stored in one or more of the other tuples in the reference table;

when it is determined that the reference identifiers have not already been stored, adds a new data identifier corresponding to one of the reference identifiers included in the added tuple to one of the plurality of identifier tables and adds new entity data corresponding to the new data identifier to the entity data group; and

when it is determined that the reference identifiers have already been stored, ends further processing of the data record after adding the reference record to the reference table without adding the new data identifier and the new entity data.

2. The database system according to claim 1, wherein

a storage area allocated to the identifier table is different from a storage area allocated to the entity data group.

3. The database system according to claim 1, wherein

values of the data identifiers are output values of a hash function that outputs a fixed-length bit string when the entity data is input.

4. The database system according to claim 1, wherein

the database includes a conversion table indicating a correspondence relation between pieces of position data indicating the storage areas of the plurality of entity data and the plurality of data identifiers, and

the transaction processing unit selects entity data from the entity data group using the conversion table and performs the transaction processing on the basis of the selection result.

5. The database system according to claim 4, wherein

the position data is an address designating the absolute position of the storage area of the entity data.

6. The database system according to claim 4, wherein

the position data is an offset designating the relative position of the storage area of the entity data.

7. The database system according to claim 1, wherein

data identifiers for searching having the same values as the plurality of data identifiers are added to the plurality of entity data, and

the transaction processing unit searches for the data identifiers for searching, selects the entity data on the basis of the search result, and performs the transaction processing on the basis of the selection result.

8. The database system according to claim 1, wherein

the plurality of data identifiers are stored in continuous storage areas of the storage unit.

9. The database system according to claim 1, further comprising:

a defragmentation unit that reads the plurality of data identifiers from the storage unit and writes the read data identifiers to continuous storage areas allocated to the identifier table when the plurality of data identifiers are dispersed and stored in a plurality of discontinuous storage areas.

10. The database system according to claim 1, wherein the plurality of entity data includes variable-length data.

11. The database system according to claim 1, wherein

each of the identifier tables includes at least one tuple that is defined in a row direction, an attribute field that is defined in a column direction and includes tuple identifiers, and an attribute field that is defined in the column direction and includes the data identifiers, and

the reference table includes at least one tuple that is defined in a row direction and at least one attribute field that is defined in a column direction and includes the reference identifiers.

12. The database system according to claim 1, wherein

the storage area allocated to the entity data group is divided into a plurality of partition areas, and

the plurality of partition areas is allocated as areas that store different types of entity data in the entity data group,

wherein each partition area stores one of the different types of entity data that is different from the different types of entity data stored in any other of the partition areas.

13. The database system according to claim 1, wherein

the database includes a plurality of sub-entity data having content related to the plurality of entity data,

the entity data and the sub-entity data having content related to the entity data are stored in continuous storage areas, and

when selecting entity data from the entity data group by searching the identifier table, the transaction processing unit reads sub-entity data having content related to the selected entity data from the database.

14. The database system according to claim 1, wherein

the database includes a plurality of sub-entity data having content related to the plurality of entity data,

a set of position data indicating the position of the storage area of the sub-entity data having content related to the entity data is added to the respective entity data, and

when selecting entity data from the entity data group by searching the identifier table, the transaction processing unit reads sub-entity data designated by the position data added to the selected entity data from the database.

15. The database system according to claim 14, wherein

the position data indicating the position of the storage area of the sub-entity data is an address designating the absolute position of the storage area of the sub-entity data.

16. The database system according to claim 14, wherein

the position data indicating the position of the storage area of the sub-entity data is an offset designating the relative position of the storage area of the sub-entity data.

17. The database system according to claim 1, wherein

the database includes at least one sub-entity data group having content related to the entity data group,

the storage unit includes a first storage area allocated to the entity data group and a second storage area allocated to the sub-entity data group, and

the transaction processing unit selects one of the first storage area and the second storage area on the basis of the received query.

18. The database system according to claim 1, wherein

the query is described with a query language, and

the transaction processing unit analyzes the query and performs, as the transaction processing, a transaction on the database on the basis of the analysis result.

19. A method of managing a database, comprising:

receiving, by a computing device including a processor, a query for a database including an entity data group containing a plurality of entity data, a plurality of identifier tables each having only fixed-length data and each having, as the fixed-length data, a reference identifier and a data identifier in each tuple that eliminates overlap with other identifier tables, and a reference table having the reference identifiers in each tuple, the data identifier uniquely indicating one of the plurality of entity data, the reference identifiers in each tuple of the reference table uniquely indicating the data identifiers in the different identifier tables,

wherein each reference identifier of the set of reference identifiers in the tuple of the reference table uniquely identifies one of the data identifiers stored in one of the identifier tables; and

performing, by the computing device, transaction processing on the database on the basis of the received query using the reference table and the identifier tables and transmitting, by the computing device, a result of the transaction processing back to a device that initiated the query,

wherein performing the transaction processing comprises;

converting a data record into a reference record including reference identifiers;

adding the reference record as one tuple to the reference table;

determining whether all of the reference identifiers included in the added tuple have already been stored in one ore more of the other tuples in the reference table;

when it is determined that the reference identifiers have not already been stored in, adds a new data identifier corresponding to one of the reference identifiers included in the added tuple to one of the plurality of identifier tables and adds new entity data corresponding to the new data identifier to the entity data group; and

when it is determined that the reference identifiers have already been stored, ends further processing of the data record after adding the reference record to the reference table without adding the new data identifier and the new entity data.

20. A non-transitory computer-readable storage medium storing a program for causing a computer to execute a database management process, the database management process comprising:

receiving a query for a database including an entity data group containing a plurality of entity data, a plurality of identifier tables each having only fixed-length data and each having, as the fixed-length data, a reference identifier and a data identifier in each tuple that eliminates overlap with other identifier tables, and a reference table having the reference identifiers in each tuple, the data identifier uniquely indicating one of the plurality of entity data, the reference identifiers in each tuple of the reference table uniquely indicating the data identifiers in the different identifier tables,

wherein each reference identifier of the set of reference identifiers in the tuple of the reference table uniquely identifies one of the data identifiers stored in one of the identifier tables; and

performing transaction processing on the database on the basis of the received query using the reference table and the identifier tables and transmitting a result of the transaction processing back to a device that initiated the query,

wherein performing the transaction processing comprises;

converting a data record into a reference record including reference identifiers;

adding the reference record as one tuple to the reference table;

determining whether all of the reference identifiers included in the added tuple have already been stored in one ore more of the other tuples in the reference table;

when it is determined that the reference identifiers have not already been stored in, adds a new data identifier corresponding to one of the reference identifiers included in the added tuple to one of the plurality of identifier tables and adds new entity data corresponding to the new data identifier to the entity data group; and

when it is determined that the reference identifiers have already been stored, ends further processing of the data record after adding the reference record to the reference table without adding the new data identifier and the new entity data.