Single repository manifestation of a multi-repository system

• US 9,690,811 B1
• Filed: 11/05/2004
• Issued: 06/27/2017
• Est. Priority Date: 11/05/2003
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Bodamer, Roger, Dahbour, Ziyad Mohammad, Templeton, Bruce Alec, Butterfield, Richard Ira
• Primary Examiner(s): LIN, SHEW FEN
• Application Number:
  US10/982,184
• Time in Patent Office: 4,617 Days
• Field of Search: 707100, 707781
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409

Abstract

Techniques are provided for manifesting a multiple repository system as a single repository to an application that is designed to use a single repository. According to one aspect, a particular container, which is used by the application to store data, is identified. One or more additional containers are created in one or more different repositories. Each of the additional containers is formatted to store the data that the application stores in the particular container. A construct is created. The construct is associated with the particular container'"'"'s identifier. The construct causes information from the particular container and each of the additional containers to be combined to answer database commands that reference the particular container'"'"'s identifier. As a result, data stored in a single repository can be distributed among multiple repositories, and the unmodified application can continue to access that data as though the data was stored in the single repository.

Claims

1. A method for selectively copying a configuration data table from one repository to another, different repository comprising:

determining, by a system including a processor, a frequency of first accesses of a particular configuration data table, wherein said first accesses occur in connection with accesses of one or more transactional data tables that are contained in a first repository that contains the particular configuration data table;

determining, by the system, a frequency of second accesses of the particular configuration data table, wherein said second accesses occur in connection with accesses of one or more transactional data tables that are contained in a second repository that does not contain the particular configuration data table; and

in response to determining that the frequency of second accesses exceeds the frequency of first accesses, copying, by the system, the particular configuration data table to the second repository.

2. The method of claim 1, wherein the particular configuration data table contains data that does not change with a transaction associated with either the first accesses or the second accesses.

3. The method of claim 2, wherein the one or more transactional data tables contained in the first repository and the one or more transactional data tables contained in the second repository contain data that can change with the transaction.

4. The method of claim 1, wherein the one or more transactional data tables in the first repository and the one or more transactional data tables in the second repository each contain values that are defined in the particular configuration data table.

5. The method of claim 1, further comprising repeating, at a specified time interval, the determining a frequency of first accesses of a particular configuration data table, the determining a frequency of second accesses of the particular configuration data table, and the copying the particular configuration data table to the second repository when the frequency of second accesses exceeds the frequency of first accesses.

6. The method of claim 1, wherein copying the particular configuration data table includes moving the particular configuration data table from the first repository to the second repository and providing a pointer in the first repository to point to the particular configuration data table in the second repository.

7. The method of claim 1, wherein copying the particular configuration data table includes modifying a schema object in the first repository to refer to an identifier of the particular configuration data table in the second repository instead of an identifier of the particular configuration data table when it was contained in the first repository.

8. The method of claim 7, further comprising, describing, in a schema object that is a logical table, a subset of information items stored in one or more of the particular configuration data table, the one or more transactional data tables in the first repository, and the one or more transactional data tables in the second repository.

9. The method of claim 8, further comprising describing the subset of information items in a manner that satisfies a Structured Query Language (SQL) statement.

10. The method of claim 1, further comprising manifesting, to an application that is designed to use a single repository, the first and second repositories as a single repository.

11. The method of claim 1, wherein the first repository is a first database and the second repository is a second database that is physically separated from the first database.

12. A multiple repository system that is manifested to an application as a single repository comprising:

a first repository that contains a particular configuration data table and one or more first transactional data tables;

a second repository that contains one or more second transactional data tables and not the particular configuration data table; and

at least one processor; and

a non-transitory storage medium storing instructions executable on the at least one processor to;

determine a frequency of first accesses of the particular configuration data table, wherein the first accesses occur in connection with accesses of the one or more first transactional data tables;

determine a frequency of second accesses of the particular configuration data table, wherein the second accesses occur in connection with accesses of the one or more second transactional data tables; and

in response to a determination that the frequency of second accesses exceeds the frequency of first accesses, copy the particular configuration data table to the second repository.

13. The system of claim 12 wherein, the one or more first transactional data tables and the one or more second transactional data tables each contain values that are defined in the particular configuration data table.

14. The system of claim 12 wherein, the at least one processor is to modify a schema object in the first repository to refer to an identifier of the particular configuration data table in the second repository instead of an identifier of the particular configuration data table when it was contained in the first repository.

15. The system of claim 14, wherein the schema object is a logical table that describes a subset of information items stored in one or more of the particular configuration data table, the one or more first transactional data tables, and the one or more second transactional data tables.

16. The system of claim 12, wherein the first repository is a first database and the second repository is a second database that is physically separated from the first database.

17. A non-transitory computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to:

determine a frequency of first accesses of a particular configuration data table, wherein said first accesses occur in connection with accesses of one or more transactional data tables that are contained in a first repository that contains the particular configuration data table;

determine a frequency of second accesses of the particular configuration data table, wherein said second accesses occur in connection with accesses of one or more transactional data tables that are contained in a second repository that does not contain the particular configuration data table; and

in response to a determination that the frequency of second accesses exceeds the frequency of first accesses, copy the particular configuration data table to the second repository.

18. The non-transitory computer-readable storage medium of claim 17, wherein the non-transitory computer-readable storage medium further comprises instructions that, when executed by the processor, cause the processor to:

modify a schema object in the first repository to refer to an identifier of the particular configuration data table in the second repository instead of an identifier of the particular configuration data table when it was contained in the first repository.

19. The non-transitory computer-readable storage medium of claim 17, wherein the instructions, when executed by the processor, cause the processor to copy the particular configuration data table by moving the particular configuration data table from the first repository to the second repository and providing a pointer in the first repository to point to the particular configuration data table in the second repository.

20. The non-transitory computer-readable storage medium of claim 17, wherein the first repository is a first database and the second repository is a second database that is physically separated from the first database.