I'm assuming the events, subscriptions, etc are the same for the
If so, could you combine the data into one table (replication, etc)
using and clientid column to indicate where it came from and then use
that as part of your matching rule? When the subscriber signs up, they
could either select it themselves or have the subscription management
app do it for them behind the scenes.
SQL Server MVP
Get up to speed quickly with SQLNS
I support PASS, the Professional Association for SQL Server.
On Mon, 14 Aug 2006 13:19:01 -0700, Isadore Schwartz
<[email protected]> wrote:
>I am looking at an application configuration that requires me to manage data
>for multiple clients as a single manager. Basically, I can have any number of
>clients I am responsible for (say 20), and I need to be able to retrieve any
>updates to data regarding those clients as it comes in. Thus, I could receive
>an update for 1 client, 5 clients, or all 20 clients all at the same time.
>My question is this. In a subscription model through SQL-NS, what would be
>the most reasonable/efficient way to manage that many clients (assuming that
>the search context would be - "give me all XXX for client YYY" in the
>I'm finding myself a little stuck functionally between having to define an
>individual susbscription for all 20 of the clients (for the single manager
>individual), or some sort of dynamic subscription that has all 20 clients as
>individual fields in the subscription.
>What do any of you feel would be the best way to work with this?