views:

212

answers:

4

i would like my windows service (to be written in .NET) to recognize when new rows are added to a specific table, but instead of pulling the data from the sql-server i would like to use a server push model.

does somebody has a hint for me how to achieve this? i am using sql server 2005.

tia

+3  A: 

The closest you'll get in Sql Server 2005 is a trigger. Sql Server 2008 also has change data capture.

Joel Coehoorn
+1  A: 

Yes, there is.

http://msdn.microsoft.com/en-us/library/ms171157%28SQL.90%29.aspx

Leahn Novash
Given that Notification Services were swiftly dropped again for the 2008 version, I'd not be recommending a new solution based on that.As marc_s posted, the SqlDependency/SqlNotificationRequest classes can be used from managed code.
Damien_The_Unbeliever
I didn't know it was dropped. It is not like I have touched it in a couple of years. However, the OP explicitly states that he is using SQL Server 2005, so it would not be a problem. That said, you are right about marc_s idea being a better one. It seems so much better to not to share the responsability with an external service.
Leahn Novash
+6  A: 

There's also the ADO.NET SqlDependency mechanism if you're using client side ADO.NET with C# or VB.NET

A SqlDependency object can be associated with a SqlCommand in order to detect when query results differ from those originally retrieved. You can also assign a delegate to the OnChange event, which will fire when the results change for an associated command. You must associate the SqlDependency with the command before you execute the command. The HasChanges property of the SqlDependency can also be used to determine if the query results have changed since the data was first retrieved.

You basically associate a SqlDependency with your SqlCommand, and provide an event handler that gets called when values that make up the result set of that SqlDependency change.

using(SqlCommand cmd = new SqlCommand(queryStatement, _conn))
{ 
   cmd.Notification = null;

   SqlDependency dependency = new SqlDependency(cmd);

   dependency.OnChange += 
       new OnChangeEventHandler(OnChange);

    ......
}

In the event handler, you can then do whathever you need to do.

void OnChange(object sender, SqlNotificationEventArgs e)
{
  SqlDependency dependency = sender as SqlDependency;

  (do whatever you need to do - e.g. reload the data)

}

Marc

marc_s
This is a great solution and very well may be the best in your situation, however, I'm pretty sure the "Server" (SQL server) is not "Pushing" anything... I'm curious, though, what *is* going on under the covers?
Mike DeFehr
@Mike: the server **is** pushing. See here: http://rusanu.com/2006/06/17/the-mysterious-notification/
Remus Rusanu
@Marc: actually Query Notifications are available to ODBC and OleDB clients too: http://msdn.microsoft.com/en-us/library/ms130764.aspx
Remus Rusanu
@Remus: excellent write-up about Sql Dependency! May I quote that in the future? :-)
marc_s
A: 

You could use a trigger with a webservice call from the database. But I have no idea how bad (if any) impact will be against the database.

Matthew Whited