I am using merge replication. What I am seeing is that there is only one
pull subscription running from the warehouse server where there should be 3.
It is overriding the pull subscription with each new pull from the database.
This is resulting in only the last pull subscription running from the
warehouse server. When I look at the push subscriptions I see 3 merge jobs
with unique names. When I look at the warehouse server pull subscriptions it
is using the same basic name but all with a - 0 at the end, not a unique
number. My assumption is that when you create a pull subscription it is not
checking for other subscriptions or is limited in the lenght of the name for
the publication? I am not sure what it is doing. I create the publications
using @@SERVERNAME+'_'+DB_NAME()+'_Grp#' to
identify each publication.
Shane
[quoted text, click to view] "Michael Cheng [MSFT]" wrote:
> Hi Shane,
>
> From your descriptions, I understood that you would like to separate one
> large subscriptions into three parts. If I have misunderstood your concern,
> please feel free to point it out.
>
> Based on my knowledge, by default, when creating the snapshot/transactional
> publication, the distribution agent will be shared between the publisher
> database and the subscriber database pair. Since you create multiple
> publications against a single database, if the subscribed database is same,
> you will just notice one distribution agent, I believe. However, when
> checking the pull subscriptions under the subscriber database, it should be
> the same number as the publications.
>
> About the shared agent concept, check the sp_addpublication sp and its
> @independent_agent parameter (set it to true).
>
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
>
> Sincerely yours,
>
> Michael Cheng
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
Hi Shane,
we can use the default option when we push the first publication to the
subscriber, when we push the other publications to the subscriber, we can
use the "No, the subscriber already schema and data" option. This way, it
will not apply the snapshot files more than one time.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
