Somebody got an idea about how to implement the following in SQL 2005? Or does anybody know of an example posted somewhere for this? In my opinion it's such a common problem, someone somewhere is bound to have written something about this somewhere (but I could nog find it).
We've got a table in a database and regularly an event happens that inserts a record in this table. At that moment a signal should be given to a .NET-service (in the form of a XML-message) which will do some intelligent stuff with this info.
In SQL 2000 I would implement a polling mechanism that every 10 secs (or some other appropriate interval) would do a select on the table to see if anything had changed. But with all the new features in 2005, I'm of the opinion that this could be done differently.
I've been looking at:
Notification Services, but this looks a bit like overkill for such a simple demand.
Query notifications from the Service Broker. But this is also a bit much because deletes are also a cause for a notification. Also all the articles I found are dealing with cache expiration. (Afterthought... maybe SELECT MAX(id) will work as defined query)
Ofcourse it would be nice if the signal is queued somewhere when the receiving service is temporarily not available.
To put a simple, a bunch of different processes can insert records in a table indicating a document is ready to be processed. Each time a new record is added a signal has to be sent to a .NET-service (in XML-form). This signal will process the document further.