Multiple Subscribers

One Publication with multiple-server subscribers (same articles).
1. Do the subscribers use the same snapshot or you have to reinitialize for
each?
2. Can the replication be scheduled at the same time without possible
latency on the publisher?
Morphius,
it depends on the transaction retention period and if anonymous subscribers
are set up or not. If you don't have anonymous subscribers, the cleanup
agent will remove the snapshot files once the last subscriber has
initialized, so you'll need to create a new snapshot. With anonymous
subscribers, the snapshot will stick around until the retention period is
reached, as will the changes made to the articles.
Not too sure what the second question means. When you talk about replication
being scheduled, do you mean a snapshot or distribution/merge
synchronization. At the same time as which process?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Paul,
The second question means synchronization of snapshots to subscribers. I
just want to make sure that the same articles are published to different
servers(subscribers). Thank you.
"Paul Ibison" wrote:

> Morphius,
> it depends on the transaction retention period and if anonymous subscribers
> are set up or not. If you don't have anonymous subscribers, the cleanup
> agent will remove the snapshot files once the last subscriber has
> initialized, so you'll need to create a new snapshot. With anonymous
> subscribers, the snapshot will stick around until the retention period is
> reached, as will the changes made to the articles.
> Not too sure what the second question means. When you talk about replication
> being scheduled, do you mean a snapshot or distribution/merge
> synchronization. At the same time as which process?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||Yes - the same articles can be sent to multiple subscribers. As far as I
know you can't guarantee that this is completely synchronized though - the
distribution agents won't necessarily all finish at the same time, even if
you have multiple processors there's no way of guaranteeing this.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .