Re: Inconsistent Double Notifications
by stamping the incoming event and carrying this across to the
notification we can tell at a glance if our problem is that the event
row has been duplicated in the notify matching rule or if we are
getting more events that we expected. We can also tell exactly which
event row was matched to what subscription rows when you have events
with no natural unique key and are doing a number of joins. This should
help to clarify what the notify function has done in the match, and is
it has done something odd.
In a previous post on this topic the problem turned out to be
unexpected behaviour from the sql event provider.
i would be very interested to see the results...
Get your notification services implementation going in minutes not