Multiple active database systems

• US 20070094237A1
• Filed: 12/13/2006
• Published: 04/26/2007
• Est. Priority Date: 12/30/2004
• Status: Abandoned Application

• Current Assignee: Teradata US, Inc. (Teradata Corporation)
• Original Assignee: NCR Corporation
• Inventors: Mitchell, Mark, Fastner, Thomas
• Application Number:
  US11/638,641
• Publication Number:
  US 20070094237A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/275 Synchronous replication

Abstract

Multiple-active database systems include at least two database systems that both store a common portion of a relational database. Each database system includes one or more data-storage facilities configured to store data forming the common portion of the relational database in one or more tables and one or more processing modules configured to manage access to the data in the data-storage facilities. One or more management components are configured to distribute database requests directed at the common portion of the relational database among the database systems and to synchronize the data across the database systems when changes are made to the data stored in at least one of the database systems.

Claims

1. A system comprising:

(a) at least two database systems that both store a common portion of a relational database, each database system comprising;

one or more data-storage facilities configured to store data forming the common portion of the relational database in one or more tables; and

one or more processing modules configured to manage access to the data in the data-storage facilities; and

(b) one or more management components configured to;

distribute database requests directed at the common portion of the relational database among the database systems; and

synchronize the data across the database systems when changes are made to the data stored in at least one of the database systems.

2. The system of claim 1, where the one or more management components are configured to deliver database requests directed at the common portion of the relational database to at least one of the database systems even when another of the database systems is not available to process requests.

3. The system of claim 2, where the one or more management components are configured to reroute database requests intended for the database system that is not available to another of the database systems.

4. The system of claim 2, where the one or more management components are configured to move at least one application process from the database system that is not available to another of the database systems.

5. The system of claim 1, where each of the database systems stores system state information indicating an operational status for that database system.

6. The system of claim 5, where the one or more management components are configured to access the system state information and use it in assessing whether the system is able to process a workload.

7. The system of claim 1, where the database systems are located in separate building structures.

8. The system of claim 1, where the database systems are located in separate cities.

9. A relational database comprising data organized in a relational manner within one or more tables, where one copy of at least a portion of the relational database is stored in a database system in a building structure at one geographical location, and where another copy of the portion of the relational database is stored in another building structure at another geographical location, and where both copies of the portion of the relational database are used concurrently to process requests issued to the relational database.

10. The database of claim 9, where at least some changes made to the copy stored at one of the geographical locations are made to the copy stored at another of the geographical locations.

11. The database of claim 9, where copies are stored in separate cities.

12. A management system for use in managing operation of at least two database systems that each stores a copy of at least a portion of a relational database, the management system comprising:

a workload-management component configured to distribute database requests directed at the relational database among the database systems;

a synchronization component configured to replicate changes made to one of the copies of the database in another of the copies; and

a system-administration component configured to monitor the database systems and assess whether any of the database systems is unavailable to process database requests.

13. A method for use in managing a relational database in which a common portion of the relational database is stored in at least two database systems, the method comprising:

storing in one or more tables in each of the database systems data that forms the common portion of the relational database;

distributing among the database systems database requests that are directed at the common portion of the relational database; and

synchronizing the data across the database systems when changes are made, to the data stored in at least one of the database systems.

14. The method of claim 13, where distributing database requests includes delivering database requests to at least one of the database systems even when another of the database systems is not available to process requests.

15. The method of claim 14, where distributing database requests includes rerouting database requests intended for the database system that is not available to another of the database systems.

16. The method of claim 14, further comprising moving at least one application process from the database system that is not available to another of the database systems.

17. The method of claim 13, further comprising storing, for each of the database systems, system state information indicating an operational status for that database system.

18. The method of claim 17, further comprising using the system state information to assess whether each database system is available to process requests.

19. The method of claim 13, where the database systems are located in separate building structures.

20. The method of claim 13, where the database systems are located in separate cities.

21. A method for use in managing a relational database that includes data organized in a relational manner within one or more tables, the method comprising:

storing a copy of at least a portion of the relational database in a database system located in a building structure at one geographical location;

storing another copy of the portion of the relational database in another building structure located at another geographical location; and

making both copies available concurrently to process requests issued to the relational database.

22. The method of claim 21, further comprising making a change to the copy stored at one of the geographical locations and replicating the change in the copy stored at another of the geographical locations.

23. The method of claim 21, where storing the copies includes storing the copies in separate cities.