microsoft.public.sqlserver.notificationsvcs
[Top] [All Lists]

Re: Duplicate notifications

Subject: Re: Duplicate notifications
From: TechJunkie
Date: Thu, 30 Aug 2007 19:26:00 -0000
Newsgroups: microsoft.public.sqlserver.notificationsvcs
Hi Wellington.
There is a quantumn for Vaccuming the Events Table and Notifications
table.
You can find it in the Application Settings part of the NS- ADF File.
If it occours before the Notification is delivered ( not created) a
duplicate Notification can be created,
please send a snippet of the ADF File.
Prabhukiran

On Aug 28, 2:26 pm, pwellington
<[email protected]> wrote:
> Hi Joe,
>
> There were 2 notifications in the notifications table and they were
> associated with the same Notification Batch Id.
>
> Pat
>
> "Joe Webb" wrote:
> > When you say that there were 2 notifications produced - were there 2
> > notifications in the notifications table? Or was there 1 notification in
> > the notification table, yet 2 were delivered to the subscriber?
>
> > --
> > Joe Webb
> > SQL Server MVP
> >http://weblogs.sqlteam.com/joew/
>
> > On Mon, 27 Aug 2007 17:24:01 -0700, pwellington wrote:
>
> > > Hi,
> > > We are experiencing a transient problem wherein duplication notifications
> > > are occaisionally generated for no dicernible reason.  It happened twice 
> > > in
> > > the last week in period where a several notifications were generated with 
> > > no
> > > problem.
>
> > > Probing the data tables revealed the following:
> > >  1) Only 1 event was generated.
> > >  2) 2 notifications were generated for the only subscriber to this
> > > particular event instance.
> > >  3) Running the rule query manual using the eventbatchID produced only 1 
> > > row
> > > that would have been inserted into the Notifications table.
> > > 4) Nothing appears to be awry with the Notification view defined or the
> > > 'Instead of insert' trigger.  (i might have missed something.)
>
> > > The use of 'read uncommited'  in the generatied view definitions is a 
> > > little
> > > unsettling.  Could this be leading to this 'phantom' notification?
>
> > > Should the distributor ThreadPoolSize be set to 1?
>
> > > For the most part NS works great.  I just need to wring out these last
> > > little snags.
>
> > > Thanks.



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