Posted by simo on 10/18/06 00:00

> Not a direct reply to your question - but have you looked into using
> Query Notifications rather than using triggers to roll your own
> notification solution? Query Notifications are designed specifically to
> notify front-end applications when the result of a query has changed.
> Note that Query Notifications work only on SQL Server 2005.
>
> Here's a link to the relevant documentation in Books Online:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/06b1c6fa-3024-4425-bd99-64b6d3c80267.htm
>
> --
> Hugo Kornelis, SQL Server MVP

Thanks for that Hugo,
The Query Notifications stuff is pretty cool and I have implemented it
and got it working - all very impressive.
I'm actually using it in a service object to check the status of
records in a specific table waiting to be updated by the UI. Where
the guy who has written the Web Front End is polling the database to
find out when my service has updated the status - but the web front end
is consuming about 30% CPU resources and the Query Notification is
using no noticable resources - so he might be doing the same thing
next.

My only problem was that the MS documentation for this was very
detailed about the internals of how all this works, but completely
lacked any useable examples - but we have google and found a few
examples that were quite good.

the best I found was at code magazine by julia lerman.
http://www.code-magazine.com/Article.aspx?quickid=0605061

Cheers

simo

[Back to original message]