Re: Scheduling delivery of messages
We had a somewhat similar situation for sending to multiple devices and
thought posting our solution may be helpful to others. We wanted to deliver
messages to our subscribers on two types of devices with one subscription.
Instead of trying to keep two subscriptions in sync that have the
appropriate device linked to them, we created our own table that links
subscriptions to devices. We join to that table when we run our event match
logic. So for each device they select each receives a notification on the
one subscriptions. Our management class we wrote handles adding and
We are using SQL 2005 NS so the new views make it nice to work with data at
a T-SQL level, but we are using the NS API's to do most of the work.
This is working well for us. Hopefully this helps generate ideas for others.
"Joe Webb" <[email protected]> wrote in message
> As Kate indicated, you can create one subscription for the SMTP
> protocol and one for the file delivery channel. These are two
> different subscriptions and can be delivered on any schedule you
> Just to clarify a minor point. The two subscriptions would produce
> *two* distinct notifications. They may be indentical in content and
> perhaps even in format if you choose. But they are still two distinct
> Joe Webb
> SQL Server MVP
> Get up to speed quickly with SQLNS
> I support PASS, the Professional Association for SQL Server.
> On 30 Nov 2005 14:54:04 -0800, "kate" <[email protected]> wrote:
>>there would be no problem in NS of setting up a scheduled subscription
>>for smtp delivery and one for file delivery. But i am puzzled as to why
>>you need them sent at different times ?
>>Get your notification services implementation going in minutes not
|<Prev in Thread]
||[Next in Thread>|
- Re: Scheduling delivery of messages,
Andy Wilbourn <=