sql server replication:
Hi Ron,
From what you just described, it sounds like your publications were
configured to use "shared agent" (which is the default). You can verify
whether this is indeed the case by going to the SEM->Tools->Manage
Publications...->double-click on your publication(s)->"Subscription Options"
tab and check whether the "Use a Distribution Agent that is independent of
other publications from this database" check-box is unchecked. When
publications are configured not to use independent distribution agents, only
one instance of the distribution agent is used to serve multiple
subscriptions to a single subscriber database from multiple publications
originating from the same publisher database. Thus, even when you start
synchronization from a particular subscription using a shared agent in SEM,
outstanding changes (or snapshots in your case) for all the shared
subscriptions will be delivered to the subscriber.
Configuring publications to used shared agent is not necessarily a bad thing
as it obviously cuts down the overhead of having multiple distribution
agents running. However, it seems strange to me that the snapshot for the
second publication is not being delivered in your case. As such, I would
really appreciate if you can verify again that the snapshot for the second
publication was indeed not delivered by going through the distribution agent
history and\or the content of subscriber even though you may decide that
independent agents will serve you better.
HTH
-Raymond
[quoted text, click to view] "SqlServer7Dev" <member46612@dbforums.com> wrote in message
news:3547339.1067641767@dbforums.com...
>
> Hello. I'm running SQL Server 7, SP4. I'm using a snapshot replication
> to replicate to 4 different SQL Servers (all running the same version).
> I created a publication and subscriptions for all 4 servers. The
> replication works exactly as I desire. However, when I create a new
> publication and add the same four subscribers, a problem arises. I'm
> able to see both publications under the Replication tab. However, when
> I start up a synchronization for any of the subscribers, it is
> triggering replication of the other publication I first set up. I have
> tried deleting and recreating the publications and subscriptions, but
> I'm still having the same problem. It's almost as if the publications
> have cross-linked id's or something where SQL Server thinks they're the
> same publication. I checked the replication directory and it is
> creating the two snapshots correctly, but the second publication is not
> being pushed out. Note that I only encountered this problem after
> installing SP4 on all the machines. Has anyone run into a similar
> problem like this or have any ideas on how I can resolve this? I'm
> assuming I should be able to have multiple publications from the same
> server to the same set of subscribers without this type of problem.
>
>
>
> Thanks in advance for any help.
>
>
>
> Regards,
>
> Ron.
>
>
> --
> Posted via
http://dbforums.com
