Trigger System For Databases Using Proxy

• US 20180307717A1
• Filed: 04/21/2017
• Published: 10/25/2018
• Est. Priority Date: 04/21/2017
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: MOYSI, Liran, COHEN, Aviram, LIRAN, Noam
• Granted Patent: US 10,558,641 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/235 Update request formulation
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data

Abstract

A proxy module for monitoring modifications to a database and external to the database includes a query processing module to monitor traffic to and from the database. The traffic includes queries to the database. The query processing module is further to identify a query corresponding to a request to modify the database. A trigger event module is to generate a trigger event based on the request. The trigger event indicates a modification of the database associated with the request. The trigger event module is further to cause the trigger event to be communicated from the proxy module to at least one entity accessing the database.

Claims

1. A proxy module for monitoring modifications to a database, wherein the proxy module is external to the database, the proxy module comprising:

a query processing module to

monitor traffic to and from the database, wherein the traffic includes queries to the database, and

identify a query corresponding to a request to modify the database; and

a trigger event module to

generate a trigger event based on the request, wherein the trigger event indicates a modification of the database associated with the request, and

cause the trigger event to be communicated from the proxy module to at least one entity accessing the database.

2. The proxy module of claim 1, wherein, to identify the query corresponding to the request to modify the database, the query processing module is further to determine whether the request corresponds to a request to at least one of insert, delete, and update data in the database.

3. The proxy module of claim 1, wherein the request to modify the database includes a request to modify at least one of a document and a row stored in the database.

4. The proxy module of claim 1, wherein the request to modify the database includes a request to modify a database table associated with the database.

5. The proxy module of claim 1, wherein, to generate the trigger event, the trigger event module is further to generate the trigger event in response to receiving the request from the query processing module.

6. The proxy module of claim 1, wherein, to generate the trigger event, the trigger event module is further to generate the trigger event in response to receiving an acknowledgement from the database that a modification was made to the database based on the request.

7. The proxy module of claim 1, wherein the trigger event includes at least one of an identifier of a document modified by the request, an identifier of a row modified by the request, an identifier of a database table modified by the request, an identifier of the database, an identifier of an entity that generated the request, and a type of modification associated with the request.

8. The proxy module of claim 1, wherein the trigger event includes an indication of whether the trigger event was generated in response to (i) the trigger event module receiving the request or (ii) the trigger event module receiving an acknowledgment from the database that a modification was made to the database based on the request.

9. The proxy module of claim 1, wherein the trigger event module provides the trigger event to a messaging module, and wherein the messaging module is further to selectively provide the trigger event to the at least one entity.

10. The proxy module of claim 9, wherein the messaging module is further to selectively provide the trigger event to the at least one entity based on a list of entities registered with the messaging module.

11. The proxy module of claim 9, wherein the messaging module is further to selectively provide the trigger event in response to a request received from the at least one entity.

12. A method for monitoring modifications to a database, the method comprising:

monitoring, external to the database, traffic to and from the database, wherein the traffic includes queries to the database;

identifying a query corresponding to a request to modify the database;

generating a trigger event based on the request, wherein the trigger event indicates a modification of the database associated with the request; and

causing the trigger event to be communicated to at least one entity accessing the database.

13. The method of claim 12, wherein identifying the query corresponding to the request to modify the database includes determining whether the request corresponds to a request to at least one of insert, delete, and update data in the database.

14. The method of claim 12, wherein the request to modify the database includes a request to modify at least one of a document and a row stored in the database.

15. The method of claim 12, wherein the request to modify the database includes a request to modify a database table associated with the database.

16. The method of claim 12, wherein generating the trigger event includes generating the trigger event in response to receiving the request.

17. The method of claim 12, wherein generating the trigger event includes generating the trigger event in response to receiving an acknowledgement from the database that a modification was made to the database based on the request.

18. The method of claim 12, wherein the trigger event includes at least one of an identifier of a document modified by the request, an identifier of a policy rule modified by the request, an identifier of a database table modified by the request, an identifier of the database, an identifier of an entity that generated the request, a type of modification associated with the request, and an indication of whether the trigger event was generated in response to (i) receiving the request or (ii) receiving an acknowledgment from the database that a modification was made to the database based on the request.

19. The method of claim 12, wherein providing the trigger event includes selectively providing the trigger event based on at least one of a list of entities registered to receive trigger events and a request received from the at least one entity.

20. A trigger proxy system for monitoring modifications to a remote database, the trigger proxy system comprising:

memory;

a processor; and

a proxy trigger application, stored in the memory and executable by the processor, configured to

monitor traffic to and from the remote database, wherein the traffic includes queries to the remote database,

identify a query corresponding to a request to modify the remote database,

generate a trigger event based on the request, wherein the trigger event indicates a modification of the remote database associated with the request, and

cause the trigger event to be communicated to at least one entity accessing the remote database.