Dropping a table from merge replication

Guys,
Merge replication server A to server B with NOSYNC option. (identities odd
at Server A and even at Server B)
I want to remove a table from merge replication.
Regards
Javed
Use sp_dropmergearticle
Regards,
Kestutis Adomavicius
Consultant
UAB "Baltic Software Solutions"
"Javed Iqbal" <javediqbal98@.hotmail.com> wrote in message news:%23GyRlsm7FHA.3752@.tk2msftngp13.phx.gbl...
Guys,
Merge replication server A to server B with NOSYNC option. (identities odd
at Server A and even at Server B)
I want to remove a table from merge replication.
Regards
Javed
|||......provided the snapshot hasn't yet been run - otherwise you'll have to drop the subscriptions first and reinitialize (nosync again so not too arduous).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks Paul,
I have set up merge replication.
Server A = Publisher
Server B = Subscriber
Snapshot = NOSYNC
The identities are manually handled ie: Odd on Server A and Even on Server B.
Due to some reason I had to remove on table from my Publication. For this i dropped subscription then removed table from publication.
Mean while I allowed user to connect to publisher and change data. After say 20 minutes i again enabled to subscription with NOSYNC.
I got an error for OBSOLETE SNAPSHOT. so I ran the snap shopt again. and since then merge agent is running fine.
My concern is between that 20 minutes data changed is not propagated to the subscriber. How do i sync my database for those records?
Regards
Javed
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:ewVZUro7FHA.252@.TK2MSFTNGP15.phx.gbl...
.....provided the snapshot hasn't yet been run - otherwise you'll have to drop the subscriptions first and reinitialize (nosync again so not too arduous).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||If the extra changes were inserts you could run sp_addtabletocontents to include the rows then resynchronise. If they are general inserts and updates, you can use sp_mergedummyupdate for each single row. It might be difficult to find these changed rows, and something like datacompare could be used for this to decide what to do.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)