Good afternoon, guys and gals;
In my all-MS-SQL2k environment, I use merge replication from publisher
(server A) to subscriber (server B), and then as a new, identical
publication from server B to subscriber (server C).
When making a schema change to Server A using sp_AddMergeArticle, I
can rerun the Snapshot agent, and get the changes to apply to the
first subscription on Server B, as advertised. However, they do not
seem to apply Server B's publication, so that Server C doesn't get the
updates without breaking and resubscribing (or using
sp_AddMergeArticle again).
Is that just the way it works, or is there some parameter on the proc
I could use to get the changes to propagate to subscribers down-
stream?
TIA!
-Joseph
Joseph - that's the way it is. Some ddl changes will get republished in SQL
Server 2005 but not adding articles like this.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Thanks, Paul!
I'll try applying the same update scripts to the second publication...
Thanks again,
Joseph
On Feb 8, 4:45 pm, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> Joseph - that's the way it is. Some ddl changes will get republished in SQL
> Server 2005 but not adding articles like this.
> Cheers,
> Paul Ibison SQL Server MVP,www.replicationanswers.com
sql
Friday, March 23, 2012
Getting sp_addmergearticle to apply to subsequent publications
Labels:
all-ms-sql2k,
apply,
database,
environment,
galsin,
guys,
merge,
microsoft,
mysql,
oracle,
publications,
publisher,
replication,
server,
sp_addmergearticle,
sql,
subscriber,
subsequent
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment