Merge replication- How to drop article and than add it again

Hi All,
I need to drop an article from live merge publication and than add it back
again with different schema (column, PK etc’) . I can’t use
sp_dropsubscription for every subscriber and sp_droparticle because it is not
transactional / snapshot publication.
Do I have any other alternative other than reinitialize the whole
publication? .
Thanks,
Eyal
Unfortunately not in the case of merge.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||There is more info here
http://msdn.microsoft.com/library/de...limpl_22pf.asp
about managing schema changes with merge replication.
Thanks
Nabila Lacey
"? ??" <nospameyalSchapira@.hotmail.com> wrote in message
news:05D80E20-9EC0-4A00-BF56-210C868F3617@.microsoft.com...
> Hi All,
> I need to drop an article from live merge publication and than add it
back
> again with different schema (column, PK etc') . I can't use
> sp_dropsubscription for every subscriber and sp_droparticle because it is
not
> transactional / snapshot publication.
> Do I have any other alternative other than reinitialize the whole
> publication? .
>
> Thanks,
> Eyal

Merge Replication Failed - Urgent Please

I have two databases A & B which have a merge replication between them. Both are live data. I wanted to alter table in db A, so i deleted subscription and altered the table from db A. After that i rebuilt the replication between A & B with initialization but now my replication fails. Every time i get different error messages..recently i get message of 'Subscriber failed to initialize'. Could anyone suggest how to resolve this? Urgent please.

Hello,

Which one is the subscriber, A or B?

What kind of alter table did you perform, such as add/drop column or change the definition of the table?

After the ALTER TABLE, the table schema is different from each other, right?

When the replication was rebuilt, was it a pull subscription or push subscription?

Thanks.

This posting is provided AS IS with no warranties, and confers no rights

|||A is the publisher and B is the subscriber. I alter the table with increasing the datatype width from 9-50 varchar. After update the schema of A is different from each other. Replication is push from publisher.|||

Try this -

Alter the table on A back to what it was.

Set up the replication with NoSync scenario, as @.sync_type = 'NONE' in the sp_addmergesubscription (see http://msdn2.microsoft.com/en-us/library/ms187717.aspx).

Make a dummy sync.

Alter table again on A to increasing the width of the desired datatype

Sync again.

Thanks,

This posting is provided AS IS with no warranties, and confers no rights