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)

Drop Stored Procedure causing Dropped Tables

Hey guys, has anyone ever seen this happen:

Try to move stored proc from one DB to another using DTS, errors on create proc. Create proc manually.

Three tables referenced by that stored proc have been dropped and re-created with the same table structure.

I'm not 100% certain that it happened at exactly the same time, but it seems to be around the same time. Any ideas? Anyone seen this happen before?You will have to check the options you picked for the Transfer task in your DTS package. Did you ask it to move dependent objects also? For more help on the DTS package/tasks, please post in the SQL Server Integration Services forum.|||It was selected for dependent objects, but those tables are not dependent on the stored proc. As far as I know, the DTS method I used was the same as using DROP PROCEDURE, since it failed after the drop.|||I don't know how the DTS task determines dependencies. If it uses say sp_depends SP then you can check by running the SP for your SP to see the dependencies. Note, that this SP only gives immediate dependencies. If this doesn't help find how DTS determines dependencies then ask in the SSIS forum or run your package and trace the calls to SQL Server.