Re: Using Triggers as event provider and notification instance state
there are probably two ways to handle this depending on your skillset.
all in TSQL - the trigger just logs the event to another table. That
table is swept regularly by a scheduled SQL hosted provider to extract
any outstanding events.
outside TSQL - the trigger drops the event to an XP which stores it on
an MSQ or in a filewatch directory which is handled by another hosted
Both methods follow the NS architecture of forward and store which
allow components to be switched off and then pick up where they left
hope that help
Get your notification services implementation going in minutes not