Routing database requests among multiple active database systems

• US 20070208753A1
• Filed: 03/16/2007
• Published: 09/06/2007
• Est. Priority Date: 12/30/2004
• Status: Abandoned Application

• Current Assignee: Teradata US, Inc. (Teradata Corporation)
• Original Assignee: NCR Corporation (NCR Voyix Corporation)
• Inventors: Mitchell, Mark, Fastner, Thomas
• Application Number:
  US11/638,330
• Publication Number:
  US 20070208753A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning

Abstract

A workload-management tool is used in distributing database requests across at least two database systems that both store copies of at least a portion of a relational database to which the database requests are directed. The tool includes one or more rules for routing database requests to the database systems and a routing component. The routing component is configured to receive an incoming database request, access the one or more rules for routing database requests to the database systems, and apply the one or more rules in selecting an appropriate one of the database systems to receive the incoming database request.

Claims

1. A workload-management tool for use in distributing database requests across at least two database systems that both store copies of at least a portion of a relational database to which the database requests are directed, the tool comprising:

one or more rules for routing database requests to the database systems; and

a routing component configured to;

receive an incoming database request;

access the one or more rules for routing database requests to the database systems; and

apply the one or more rules in selecting an appropriate one of the database systems to receive the incoming database request.

2. The workload-management tool of claim 1, where the rules for routing database requests are configured to ensure that all of the database systems available to process requests receive at least some of the database requests.

3. The workload-management tool of claim 1, where the rules for routing database requests include one or more identification-based rules that map each incoming database request to at least one of the database systems according to an identification of the request'"'"'s originating source.

4. The workload-management tool of claim 3, where the routing component is configured to:

obtain the identification of the request'"'"'s originating source; and

apply the one or more identification-based rules to the identification of the request'"'"'s originating source in selecting an appropriate one of the database systems to receive the request.

5. The workload-management tool of claim 1, where the rules for routing database requests include a round-robin rule configured to ensure selection of the database systems in an alternating pattern.

6. The workload-management tool of claim 1, where the routing component includes at least two elements:

a first element configured to assess the distribution of database-workload tasks among the database systems and use this assessment in selecting one or more of the database systems that are appropriate to receive the incoming database request; and

a second element configured to access one or more predefined request-distribution rules and apply these rules in selecting one or more of the database systems that are appropriate to receive the incoming database request.

7. The workload-management tool of claim 6, where the second element is configured to select an appropriate one of the database systems from among the one or more database systems selected by the first element.

8. The workload-management tool of claim 1, where the routing component is configured to:

conclude that the database system selected to receive the incoming database request is not available to process the request; and

apply the one or more rules to select another of the database systems to receive the incoming database request.

9. A workload-management tool for use in distributing database-workload tasks across at least two database systems that both store copies of at least a portion of a relational database to which the database-workload tasks are directed, the tool comprising:

a first element configured to assess the distribution of database-workload tasks among the database systems and to use this assessment in selecting one or more of the database systems to perform a particular workload task; and

a second element configured to access one or more predefined workload-distribution rules and apply these rules in selecting one or more of the database systems to perform the particular workload task.

10. The workload-management tool of claim 9, where the second element is configured to select an appropriate one of the database systems from among the one or more database systems selected by the first element.

11. The workload-management tool of claim 9, where the second element is configured to apply a round-robin rule for selection of the database systems in an alternating pattern.

12. The workload-management tool of claim 9, further comprising a protection element configured to receive an indication that a request cannot be completed on one of the database systems and, in response, to reroute the request to another of the database systems.

13. The workload-management tool of claim 9, further comprising a partitioning element configured to enforce one or more database-access rules that allow a greater level of access to the copy of the relational database stored in one of the database systems than to the copy of the relational database stored in another of the database systems.

14. The workload-management tool of claim 13, where the one or more database-access rules include a rule that allows a user to view at least a portion of a database table in the one database system and view a smaller portion of the database table in the other database system.

15. A method for use in distributing database requests across at least two database systems that both store copies of at least a portion of a relational database to which the database requests are directed, the method comprising:

receiving an incoming database request;

accessing one or more rules for routing database requests to the database systems; and

applying the one or more rules in selecting an appropriate one of the database systems to receive the incoming database request.

16. The method of claim 15, where applying the one or more rules includes applying a rule to ensure that all of the database systems available to process requests receive at least some of the database requests.

17. The method of claim 15, where applying the one or more rules includes applying one or more identification-based rules that map each incoming database request to at least one of the database systems according to an identification of the request'"'"'s originating source.

18. The method of claim 17, further comprising:

obtaining the identification of the request'"'"'s originating source; and

applying the one or more identification-based rules to the identification of the request'"'"'s originating source to select an appropriate one of the database systems to receive the request.

19. The method of claim 15, where applying the one or more rules includes applying a round-robin rule to ensure selection of the database systems in an alternating pattern.

20. The method of claim 15, where applying the one or more rules includes:

assessing the distribution of database-workload tasks among the database systems and using this assessment to select one or more of the database systems that are appropriate to receive the incoming database request; and

accessing one or more predefined request-distribution rules and applying these rules to select one or more of the database systems that are appropriate to receive the incoming database request.

21. The method of claim 20, where applying the one or more predefined request-distribution rules includes selecting an appropriate one of the database systems from among the one or more database systems that are selected after assessing the distribution of database-workload tasks.

22. The method of claim 15, further comprising:

concluding that the database system selected to receive the incoming database request is not available to process the request; and

applying the one or more rules to select another of the database systems to receive the incoming database request.

23. A method for use in distributing database-workload tasks across at least two database systems that both store copies of at least a portion of a relational database to which the database-workload tasks are directed, the tool comprising:

assessing the distribution of database-workload tasks among the database systems and using this assessment to select one or more of the database systems to perform a particular workload task; and

accessing one or more predefined workload-distribution rules and applying these rules in selecting one or more of the database systems to perform the particular workload task.

24. The method of claim 23, where applying the one or more predefined workload-distribution rules includes selecting an appropriate one of the database systems from among the one or more database systems that are selected after assessing the distribution of database-workload tasks.

25. The method of claim 23, where applying the one or more predefined workload-distribution rules includes applying a round-robin rule to ensure selection of the database systems in an alternating pattern.

26. The method of claim 23, where assessing the distribution of database-workload tasks includes assessing availability of database-system resources within each of the database systems and using this assessment to distribute application processes among the database systems.

27. The method of claim 23, further comprising enforcing one or more database-access rules that allow a greater level of access to the copy of the relational database stored in one of the database systems than to the copy of the relational database stored in another of the database systems.

28. The method of claim 27, where enforcing the one or more database-access rules includes enforcing a rule that allows a user to view at least a portion of a database table in the one database system and view a smaller portion of the database table in the other database system.