RESTRICTING QUERIES BASED ON COST OF PERFORMANCE

• US 20110010360A1
• Filed: 07/10/2009
• Published: 01/13/2011
• Est. Priority Date: 07/10/2009
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: JONES, WILLARD BRUCE, WATSON, ANDREW SEAN, SKARIA, SIMON, KANNAN, NARESH, AYOUB, DINA A.M., XUE, MINGQUAN
• Application Number:
  US12/501,318
• Publication Number:
  US 20110010360A1
• Time in Patent Office: Days
• US Class Current: 707/719
• CPC Class Codes: G06F 16/24542 Plan optimisation
• CPC Class Codes: G06F 16/24544 Join order optimisation

Abstract

Queries that are determined to be too expensive to perform are prevented from being executed. Queries are determined to be too expensive based on the resources that are required to perform the query. For example, the query may be determined to be too expensive to perform based a length of a list the query requires to access, a number of lookups that may be performed relating to the query, a number of unique permissions accessed by the query, and the like. Queries that are deemed to expensive during normal operation may be performed during other times such that the impact of performing the query on other users is limited.

Claims

1. A method for improving performance of a server performing queries related to interacting with data in a database, the method executing on a processor of a computer, comprising:

receiving a query at the server from a client;

wherein the query interacts with a list within the database;

determining a cost of the query;

wherein determining the cost of the query comprises determining a cost of executing the query and determining a cost of other operations that are performed in response to running the query; and

preventing the query from executing when the cost is determined to be expensive.

2. The method of claim 1, wherein determining the cost of the query comprises determining when the query requires access to a number of rows that exceed a user configurable row limit.

3. The method of claim 1, wherein determining the cost of the query comprises determining when the query requires access to a number of unique permissions that exceed a configurable unique permissions limit.

4. The method of claim 1, wherein determining the cost of the query comprises determining when the query requires a number of joins that exceed a configurable number of joins limit.

5. The method of claim 1, wherein determining the cost of the query comprises determining:

when the query requires;

access to a number of rows that exceed a user configurable row limit;

access to a number of unique permissions that exceed a configurable unique permissions limit; and

a number of joins that exceed a configurable number of joins limit.

6. The method of claim 1, wherein determining the cost of the query comprises determining a number of database requests is required to be performed in performing the query.

7. The method of claim 1, further comprising providing a predetermined time period of a day during which the determining cost operation is not performed, wherein the predetermined time period can change day to day.

8. The method of claim 5, wherein the row limit, the permissions limit, and the joins limit is a higher value for an authorized user as compared to an non-authorized user.

9. A computer-readable storage medium having computer-executable instructions for improving performance of a server performing queries related to interacting with data in a database, the instructions executing on a processor of a computer, comprising:

receiving a query to interact with the data within the database;

determining when a query is expensive by determining a cost of executing the query that relates to a number of accesses to the database; and

preventing the query from executing when the query is determined to be expensive.

10. The computer-readable storage medium of claim 9, wherein determining when the query is expensive comprises determining when the query requires access to a number of rows that exceed a row limit.

11. The computer-readable storage medium of claim 10, wherein determining when the query is expensive comprises determining when the query requires access to a number of unique permissions that exceed a unique permissions limit.

12. The computer-readable storage medium of claim 10, wherein determining when the query is expensive comprises determining when the query requires a number of joins that exceed a number of joins limit.

13. The computer-readable storage medium of claim 9, wherein determining when the query is expensive comprises determining:

when the query requires;

access to a number of rows that exceed a user configurable row limit;

creation of unique permissions that exceed a configurable unique permissions limit; and

a number of joins that exceed a configurable number of joins limit.

14. The computer-readable storage medium of claim 13, further comprising providing a predetermined time period of a day during which the determining when the query is expensive is not performed, wherein the predetermined time period can change day to day and is set to a non-peak time.

15. The computer-readable storage medium of claim 13, further comprising utilizing an object model to override one or more of the limits.

16. A system for restricting execution of queries, comprising:

a processor and a computer-readable medium;

an operating environment stored on the computer-readable medium and executing on the processor;

a network connection;

a relational database;

a content management application and a query manager operating on the processor; and

configured to perform tasks, comprising;

receiving a query to interact with data within the relational database;

determining when a query is expensive by determining a cost of the query and determining when an impact of performing the query exceeds a predetermined threshold; and

preventing the query from executing when the query is determined to be expensive.

17. The system of claim 16, wherein determining when the query is expensive comprises determining when the query requires access to a number of rows within the relational database that exceed a row limit.

18. The system of claim 17, wherein determining when the query is expensive comprises determining when the query requires a number of joins that exceed a number of joins limit.

19. The system of claim 16, wherein determining when the query is expensive comprises determining:

when the query requires;

access to a number of rows that exceed a user configurable row limit;

access to a number of unique permissions that exceed a configurable unique permissions limit; and

a number of joins that exceed a configurable number of joins limit.

20. The system of claim 19, further comprising utilizing an object model to override one or more of the limits;

providing a predetermined time period of a day during which the determining when the query is expensive is not performed, wherein the predetermined time period can change day to day and is set to a non-peak time; and

providing an error message when one of the limits is determined to be exceeded.