Re: Scheduled notification
Hi Shyam -
No doubt; without joining to the events table, every subscription in the
scope will receive a notification.
But given the OP's ADF snippet, I suspect that the app is not going to
produce the results he's expecting. For instance, the notification class
is looking for fields called name1, id1, and age1, yet in the matching
rule it's passing literals.
Maybe I'm reading too much into this and making some assumptions I
shouldn't, but I think if this were my app to debug, I'd likely start
with the matching rule and go from there. Of course, the OP didn't
really share what the app is designed to do so I may be leaping to
invalid conclusions here.
I'd certainly agree that it is often the case that when scheduled
subscriptions don't appear as expected, it's because no scheduled
subscriptions exist that meet the matching criteria.
Thanks Shyam! I'm glad you monitor this group!
SQL Server MVP
Get up to speed quickly with SQLNS
Shyam Pather [MSFT] wrote:
I don't think this is the problem - not joining an events chron and
filtering on an event condition just means the rule will generate
notifications for all subcriptions in scope.
As I said in my previous post, I think it's a schedule problem.