MANAGING EXCESS CAPACITY OF DATABASE SYSTEMS IN A CAPACITY CONTROLLED COMPUTING ENVIRONMENT

• US 20130085984A1
• Filed: 09/30/2011
• Published: 04/04/2013
• Est. Priority Date: 09/30/2011
• Status: Active Grant

• Current Assignee: Teradata Corporation
• Original Assignee: Teradata Corporation
• Inventors: Burger, Louis, Brown, Douglas P., Julien, Thomas, Vandervort, Frank Roderic
• Granted Patent: US 9,747,334 B2
• Time in Patent Office: Days
• US Class Current: 707/609
• CPC Class Codes: G06F 16/2453 Query optimisation
• CPC Class Codes: G06F 16/24547 Optimisations to support specific applications; Extensibility of optimisers

Abstract

Excess capacity available to a database system in a capacity controlled environment can be effectively managed. In particular, excess capacity that is not made available for normal operations of a database system can be used to manage errors, especially situations that may hinder expected performance of the database system. In addition, excess capacity can be used to optimize or further optimize database queries, especially those that meet a criterion (e.g., not fully optimize, not optimized as expected).

Claims

1. A computer-implemented method for managing capacity of a database system that includes one or more database nodes operable to process data associated with a database, wherein the database system is configured to operate at a limited capacity below its full capacity, and wherein the computer-implemented method comprises:

determining whether to allow excess capacity available to the database system to be used to perform one or more operations associated with processing of the data by the one or more database nodes; and

allowing the excess capacity to be used to perform the one or more operations when the determining determines to allow the allow excess capacity available to the database system to be used to perform the one or more operations associated with processing of the data by the one or more database nodes.

2. The computer-implemented method of claim 1, wherein the one or more operations pertain to processing a database query that has encountered an error.

3. The computer-implemented method of claim 1, wherein the one or more operations pertain to optimization of a database query.

4. The computer-implemented method of claim 1, wherein the allowing the access capacity to be used to perform the one or more operations only allows the excess capacity to be used to perform the one or more operations.

5. The computer-implemented method of claim 1, wherein the allowing the access capacity to be used to perform the one or more operations comprises:

not allowing at least one or more operations associated with the database to use the excess capacity.

6. The computer-implemented method of claim 1, wherein the determining whether to allow excess capacity available to the database system to be used to perform one or more operations comprises:

determining whether an error condition has occurred.

7. The computer-implemented method of claim 6, wherein the error condition is associated with scheduling a database query for execution.

8. The computer-implemented method of claim 1, wherein the determining whether to allow excess capacity available to the database system to be used to perform one or more operations comprises:

determining whether to optimize or further optimize a database query.

9. The computer-implemented method of claim 1, wherein the determining whether to allow excess capacity available to the database system to be used to perform one or more operations comprises one or more of the following:

(a) identifying an execution plan with an estimated completion time that does meet a goal or a requirement,

(b) identifying an execution plan with an execution time and/or resource consumption time that exceed a threshold, and

(c) Identifying a query that a number of operations that exceed a threshold.

10. An apparatus, comprising:

one or more processors operable to;

process and store data for a database system configured to operate at a limited capacity below its full capacity;

determine whether to allow excess capacity available to the database to be used to perform one or more operations associated with the database; and

allow the excess capacity to be used to perform the one or more operations when the determining determines to allow the allow excess capacity available to the database system to be used to perform the one or more operations associated with the database.

11. The apparatus of claim 10, wherein the one or more operations pertain to processing a database query that has encountered an error.

12. The apparatus of claim 10, wherein the one or more operations pertain to optimization of a database query.

13. The apparatus of claim 10, wherein the allowing the access capacity to be used to perform the one or more operations only allows the excess capacity to be used to perform the one or more operations.

14. The apparatus of claim 10, wherein the allowing the access capacity to be used to perform the one or more operations comprises:

not allowing at least one or more operations associated with the database to use the excess capacity.

15. The apparatus of claim 10, wherein the determining whether to allow excess capacity available to the database system to be used to perform one or more operations comprises:

determining whether an error condition has occurred.

16. The apparatus of claim 15, wherein the error condition is associated with scheduling a database query for execution.

17. The apparatus of claim 10, wherein the determining whether to allow excess capacity available to the database system to be used to perform one or more operations comprises:

determining whether to optimize or further optimize a database query.

18. A non-transient computer readable storage medium storing at least executable computer code for managing capacity of a database system that includes one or more database nodes operable to process data associated with a database, wherein the database system is configured to operate at a limited capacity below its full capacity, and wherein the non-transient computer readable storage medium includes:

executable computer code operable to determine whether to allow excess capacity available to the database system to be used to perform one or more operations associated with processing of the data by the one or more database nodes; and

executable computer code operable to allow the excess capacity to be used to perform the one or more operations when the determining determines to allow the allow excess capacity available to the database system to be used to perform the one or more operations associated with processing of the data by the one or more database nodes.

19. The A non-transient computer readable storage medium of claim 18, wherein the one or more operations pertain to processing a database query that has encountered an error.

20. The A non-transient computer readable storage medium of claim 19, wherein the database query is selected as a result of scheduling mistake due to a limitation of an estimation technology used to estimate resource usage of the database query.

21. The A non-transient computer readable storage medium of claim 18, wherein the one or more operations pertain to optimization of a database query.

22. A non-transient computer readable storage medium of claim 21, wherein the database query is a selected database query requiring a more extensive and through optimizations than a plurality of other database queries.