I presume SQL Server 2008, so a data driven subscription is probably your choice.
You will see that MS dropped Notification Services, as no one used it. Good luck! Greg Wood [email protected] 0417044439 On Mon, Mar 28, 2011 at 5:06 PM, Stephen Liedig <[email protected]> wrote: > Grant, > Another way to do it would be to "push" changes to your application based on > an "update event" occurring in your system. Whenever data changes, publish a > "my data has just been updated event" and notify your clients of the update. > This would negate the need to do unnecessary polling and remove the > dependency on any caching mechanisms (which is not to say you can't use > caching to store your data). > - Steve > > On 27 March 2011 23:33, Grant Molloy <[email protected]> wrote: >> >> Hi list, >> I'm looking to have an application automagically update it's view of the >> data when the data in the connected database table changes. >> I've seen two main ways to do this so far. >> 1. Poll the database every n seconds >> 2. Use the System.Web.Caching.SqlDependancy object. >> Does anyone else know of any other better or smarter way of doing this ? >> thanks >> Grant >
