--- Ben Kloosterman <[EMAIL PROTECTED]> wrote: > The most common way is to get a service to poll the DB , complicating > the DB side with triggers etc is something better avoided IMHO .
But you can use triggers to aid the polling by having them do something very simple, fast and reliable, such as dropping an "event" in a polled table. At very high transaction rates, it could add to the list of issues to deal with, but pretty much any mechanism is going to do that and this approach might be easier than trying to watch for changes in a table. I wonder specifically what notification services does to accomplish this? ===== Philip - http://blogs.xcskiwinn.org/panmanphil "There's a difference between righteous anger and just being crabby" - Barbara =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
