Providing change notifications to an entity-regarding a change of a specific type to data in a relational database

• US 7,543,003 B2
• Filed: 08/25/2005
• Issued: 06/02/2009
• Est. Priority Date: 08/25/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Singh, Siddhartha, Ryseff, James D., Luo, Chang, Klein, Johannes, Shukla, Amit, Ellis, Nigel R., Acharya, Srinivasmurthy P., Fang, Lijiang, Yuan, Hua
• Primary Examiner(s): CHANNAVAJJALA, SRIRAMA T
• Application Number:
  US11/211,869
• Publication Number:
  US 20070050392A1
• Time in Patent Office: 1,377 Days
• Field of Search: 707/1, 707 3- 6, 707/9, 707/100, 707/102, 707/103.R, 707/203, 707205-206, 706 45- 50, 715/968, 719/314, 719/318
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99939 Privileged access
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A framework for data change notification includes a notification queue storing event notifications. Client applications can request event information regarding various data change events. For example, a client application can subscribe, via one or more APIs, to receive event information. The framework allows for session specific event notification mechanisms as well as durable event notification mechanisms that can be preserved across client sessions as well as server restarts. Innovative aspects of this invention include guaranteed delivery of event notifications, APIs to allow applications get summary of past events on the subscribed objects, automatic garbage collection/cleanup of notifications when a client session terminates.

Claims

1. A computer-implemented method for providing change notifications to an entity-regarding a change of a specific type to data in a relational database, said method comprising:

receiving entity registration information from an entity requesting notification of data change events in a relational database, said registration information comprising information identifying said entity, information regarding whether the entity is registered as a durable entity or non-durable entity, and information that specifies a specific type of change to data in the relational database for which notification is requested;

monitoring for an occurrence of said specific type of change to data in the relational database;

providing change notification data to said entity, by storing said change notification data in a queue, regarding a change in said relational database of said specific type for which notification is requested, wherein said queue comprises additional change notification information items, each of said additional change notification information items corresponding to said entity;

deleting any of said additional change notification information in said queue corresponding to said entity, when said entity is registered as a non-durable entity and a connection to said entity is terminated;

when said entity is registered as a durable entity;

determining that a connection to said entity is terminated;

determining that a new connection to said entity exists; and

providing said additional change notification information items corresponding to said entity using said new connection;

persistently maintaining the entity registration information for said entity across a plurality of sessions, if said entity is registered as a durable entity; and

removing the entity registration for said entity after termination of a session for which the entity registration information was created, if said entity is registered as a non-durable entity.

2. The method of claim 1, where said step of providing change notification data to said entity comprises:

responding to a request for data from said queue.

3. The method of claim 2, where said step of responding to a request for data from said queue comprises:

responding to a wait-for query executed on said queue.

4. The method of claim 1, where said step of responding to a request for data from said queue comprises:

determining using the entity registration information whether said request issued from said entity.

5. The method of claim 1, where said change involves a specific item in said relational database, where access to said specific item in said relational database is limited by a security requirement, said method further comprising:

determining that said entity fulfills said security requirement.

6. A system implemented at least in part on a processor, comprising:

subscription table storage storing entity registration information regarding an entity requesting notification of a change event in a database, said registration information comprising information identifying said entity, information regarding whether said entity is registered as a durable entity or a non-durable entity, and change information regarding at least one change definition, said change definition defining one or more possible changes to said database for which notification is requested by said entity;

a notification dispatcher, said notification dispatcher operatively connected to said subscription table storage, said notification dispatcher operatively connected to said database, and said notification dispatcher querying said database for database changes pertaining to said change definitions and receiving data regarding a pertinent change; and

a notifier, operatively connected to said notification dispatcher, said notifier operatively connected to said entity, said notifier providing at least one notification regarding said pertinent change to said entity during a current session for which the entity registration information was created, wherein;

said notifier comprises a queue storing at least one of said at least one notification regarding said pertinent change;

said queue receives queries from said entity;

said provision of at least one notification regarding said pertinent change is in response to said query;

the entity registration information for said entity is persistently maintained in the subscription table storage after termination of the current session, if said entity is registered as a durable entity; and

the entity registration for said entity is removed from the subscription table storage after termination of the current session, if said entity is registered as a non-durable entity.

7. The system of claim 6, further comprising:

a service broker, said service broker, if said operative connection between said notifier and said entity is terminated, removing all pertinent changes corresponding to said entity from said queue, if said entity is registered as a non-durable entity.

8. A computer-readable storage medium comprising computer-executable instructions that are executable by a computer for performing the steps of:

receiving entity registration information from an entity requesting notification of data changes in a relational database, said registration information comprising information identifying said entity, information regarding whether said entity is registered as a durable entity or a non-durable entity, and information that specifies a specific type of change to data in the relational database for which notification is requested;

monitoring for an occurrence of said specific type of change to data in the relational database;

providing change notification data to said entity, by storing said change notification data in a queue, regarding a change in said relational database of said specific type for which notification is requested, wherein said queue comprises additional change notification information items, each of said additional change notification information items corresponding to said entity;

deleting any of said additional change notification information in said queue corresponding to said entity, when said entity is registered as a non-durable entity and a connection to said entity is terminated;

when said entity is registered as a durable entity;

determining that a connection to said entity is terminated;

determining that a new connection to said entity exists; and

providing said additional change notification information items corresponding to said entity using said new connection;

persistently maintaining the entity registration information for said entity across a plurality of sessions, if said entity is registered as a durable entity; and

removing the entity registration for said entity after termination of a session for which the entity registration information was created, if said entity is registered as a non-durable entity.

9. The computer-readable storage medium of claim 8, wherein:

said notification data further comprises time data identifying a point in time;

said request for data comprises a range of time;

said time data for each of said responsive notification data items is contained in said range;

said request is a wait-for request on said queue; and

the computer-executable instructions further configured to provide an API (application programming interface) method for an entity to register as one of said possible requesting entities.

10. The computer readable storage medium of claim 8, further comprising:

providing an API (application programming interface) for one of said possible requesting entities to register a change definition corresponding to said entity.

11. The computer-readable storage medium of claim 8, where said step of providing data change data regarding said data change to one of said requesting entities is performed only after it is determined that said one of said requesting entities has access privileges to said data change data.