[Top] [All Lists]

Re: Notification resend logic

Subject: Re: Notification resend logic
From: Joe Webb
Date: Wed, 20 Jul 2005 19:10:20 -0500
Newsgroups: microsoft.public.sqlserver.notificationsvcs
Hi RDV - 

You have an interesting application. 

IMHO, I think you're best solution is the one that you've already
found -  using Chron tables. The Chron tables allow you to keep state
and even though it may seem a bit redundant in your case, it will
likely be more efficient (assuming optimized T-SQL) than another

BTW - generally speaking a query with ... NOT EXISTS (SELECT...) is
more efficient than one with ...NOT IN (SELECT...). You may want to
consider changing that in your T-SQL.


Joe Webb
SQL Server MVP

Get up to speed quickly with SQLNS 

I support PASS, the Professional Association for SQL Server.

On 20 Jul 2005 14:34:11 -0700, "kate" <[email protected]> wrote:

>this is interesting , as you seem to need to suppress the notifications
>for a particular subscriber until the defined time interval has passed
>since the last notfication.
>Rather than use chronicles which are event based, I think you could add
>a field to the subscription schema to contain the last-sent-time and
>then update that from a custom delivery protocol assembly using
>information from the notification fields to locate the matching
>subscription. The same information can then be used in the custom
>delivery protocol to suppress those notifications which occur prior to
>the time limit.
>hope this helps
>Kate MBCS
>Alert Technologies
>Get your notification services implementation going in minutes not
>weeks ......

<Prev in Thread] Current Thread [Next in Thread>