METHOD OF OPTIMIZING THE INTERACTION BETWEEN A SOFTWARE APPLICATION AND A DATABASE SERVER OR OTHER KIND OF REMOTE DATA SOURCE

• US 20130325927A1
• Filed: 02/22/2011
• Published: 12/05/2013
• Est. Priority Date: 02/22/2010
• Status: Active Grant

• Current Assignee: Data Accelerator Ltd.
• Original Assignee: Data Accelerator Ltd.
• Inventors: Elliott, Edward Philip Edwin, Corbett, Sean P., Clothier, Matthew P.
• Granted Patent: US 9,396,228 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2453 Query optimisation
• CPC Class Codes: G06F 16/24539 using cached or materialised query results
• CPC Class Codes: H04L 67/01 Protocols

Abstract

The invention is a method of optimizing the interaction between (i) a client, being an application such as database software, implemented on a computing device, and (ii) database server software implemented on a computing device. Query data is routed from the client to the database server software through an optimisation system implemented on a computing device and then response data provided by the database server software is routed to the optimisation system. The optimisation system analyses that (or later) query data and, based on that analysis, applies rules to response data provided by the database server software, in order to generate optimised response data to thereby speed up the interaction between the client and the database server software.

Claims

1. A method comprising:

routing query data from a client to a database server through an optimisation system implemented on a computing device;

routing response data corresponding to the query data provided by the database server to the optimisation system;

analysing, by the optimisation system, the query data;

applying rules, by the optimisation system, to the response data based on analysis of the query data, in order to generate optimised response data and speed up interaction between the client and the database server.

4. The method of claim 1 further comprising, decoding the query data and/or response data to generate content and/or context data of the query data and/or the response data, the content and/or context data including as the client and/or server understands the query data and/or response data, to provide relevant optimisation.

5. The method of claim 1 wherein, the query data includes the actual query that the client has asked to be run or the request for data that the client has asked for.

6. The method of claim 1 wherein, context of the query data includes whether a query, included as part of the query data, is a part of a series of requests generated by the client and relationships between the requests.

7. The method of claim 1 wherein the context of query data includes environmental details such as which server a request included as part of the query data is going to, which user and workstation sent the request and network link speeds.

8. The method of claim 1 further comprising, determining, by the optimisation system based on context of the response data, the effectiveness of specific rules applied to specific requests, in order to either change parameters of rules or enable or disable one or more of the rules.

11. The method of claim 1 further comprising, optimising the interaction between the client and the database server to enable a practical connection to be made over a slow link or a high latency link.

14. The method of claim 11, wherein optimising the interaction between the client and the database server further includes speeding up flow of data, causing cessation of the flow of data, obviating a need for data to flow, or managing the flow of data.

35. The method of claim 1, wherein the query and response data includes database management server requests and responses.

57. The method of claim 1, wherein the rules are applied based on factors such as initiator and server addresses or locations, time of day, configuration, server load, and a combination of these.

58. The method of claim 1, wherein the rules are applied at different points in a request/response stream.

63. The method of claim 11 wherein the slow link or the high latency link is over a wide area network or the Internet.

2-3. -3. (canceled)

9-10. -10. (canceled)

12-13. -13. (canceled)

15-34. -34. (canceled)

36-56. -56. (canceled)

59-62. -62. (canceled)

64. A system comprising:

a client;

a database server including database server software configured to receive query data generated by the client;

an optimisation system coupled between the client and database server, the optimisation system configured to;

receive the query data from the client and send the query data to the database server;

receive response data corresponding to the query data from the database server;

analysing the query data received from the client;

applying rules to the response data based on the analysis of the query data in order to generate optimised response data, and speed up interaction between the client and the database server software.

65. The system of claim 64, wherein the optimisation system is further configured to decode the query data and/or response data to generate content and/or context data of the query data and/or the response data, the content and/or context data including as the client and/or server understands the query data and/or response data to provide relevant optimisation.

66. The system of claim 64, wherein the query data includes the actual query that the client has asked to be run or the request for data that the client has asked for.

67. The system of claim 64, wherein context of the query data is selected from a group consisting of whether a query, included as part of the query data, is a part of a series of requests generated by the client, a relationship between the requests, and a combination of these.

68. The system of claim 64, wherein content of the request data includes environmental details selected from the group consisting of which server a request included as part of the request data is going to, which user and workstation sent the request, network link speed, and a combination of these.

69. The system of claim 64, wherein the optimisation system is further configured to determine effectiveness of specific rules applied to specific requests based on context of the response data in order to either change the parameters of the rules or enable or disable them.

70. The system of claim 64, wherein the optimisation system is further configured to optimize the interaction between the client and the database server software to enable a practical connection to be made over a slow link or a high latency link such as the Internet, optimizing the interaction further including speeding up flow of data between the client and the database server software, causing the cessation of the flow of data, obviating the need for data to flow, or managing the flow of data.

71. The system of claim 64, wherein the query and response data includes database management server requests and responses.

72. The system of claim 64, wherein the optimisation system is further configured to apply rule based on factors such as initiator and server address or locations, time of day, configuration, and/or server load.

73. The system of claim 64, wherein the optimisation system is further configured to apply the rules at different point in a request/response stream.

74. A system comprising:

means for routing query data from a client to a database server software of a database server through an optimisation system implemented on a computing device;

means for routing response data corresponding to the query data provided by the database server software to the optimisation system,

means for analysing the query data;

means for applying rules to the response data based on analysis of the query data, in order to generate optimised response data and speed up the interaction between the client and the database server software.