The SQL Server driver for ADO.NET has the SqlDependency class. It enables applications to receive notifications when there is a change in a query result set, schema objects, or the state of the database. Using SqlDependency, an application can maintain the validity of the client-side cache easily. At one of my clients we aren't using SQL Server but Oracle. As I searched throught the standard ADO.NET driver for Oracle (System.Data.Oracle) I couldn't find a similar class.
After some digging on the Oracle site I found that Oracle has a separate driver for .NET next to the standard ADO.NET driver. If you download the Oracle Data Provider for .NET (Oracle.DataAccess) you'll find the OracleDependency class that has the same functionality as the SqlDependency class.
A simple example to show this functionality:
1: public class Notification
2: {
3: public static bool IsNotified = false;
4:
5: public static void Main(string[] args)
6: {
7: //To Run this sample, make sure that the connecting user hase change notification privilege
8: string constr = "User Id=scott;Password=tiger;Data Source=oracle";
9: OracleDependency dep = null;
10:
11: try
12: {
13: using(var con = new OracleConnection(constr))
14: {
15: var cmd = new OracleCommand("select * from table", con);
16: con.Open();
17:
18: OracleDependency.Port = 1005;
19: dep = new OracleDependency(cmd);
20: dep.OnChange += Notification.OnMyNotificaton;
21:
22: cmd.ExecuteNonQuery();
23:
24: var txn = con.BeginTransaction();
25:
26: string updateCmdText = "update table set column1 = 1 where column2 = 2";
27: OracleCommand updateCmd = new OracleCommand(updateCmdText, con);
28: updateCmd.ExecuteNonQuery();
29: txn.Commit();
30: }
31: }
32: catch (Exception e)
33: {
34: Console.WriteLine(e.Message);
35: }
36:
37: // Loop while waiting for notification
38: while(Notification.IsNotified == false)
39: {
40: Thread.Sleep(100);
41: }
42: }
43:
44: public static void OnMyNotificaton(object sender, OnChangeEventArgs arg)
45: {
46: Console.WriteLine("Notification Received");
47: DataTable changeDetails = arg.Details;
48: Console.WriteLine("Data has changed in {0}", changeDetails.Rows[0]["ResourceName"]);
49: Notification.IsNotified = true;
50: }
51: }
As every change notification registration consumes database memory, storage or network resources, or some combination thereof, it's important to be carefull when using this feature. In order to scale well with a large number of mid-tier clients, use it only for a few tables that change infrequently.