Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Drop merge repliaction the right way


Drop merge repliaction the right way

Author
Message
Knut_knut
Knut_knut
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 355
Hi

i am about to drop a merge replication and rebuild it with new snapshot and DB.
Replication Server A - B Using Merge repliaction update every 3' min.
It's not working, rather then trying to find the error we diecdecidedrop it since it doesent work anyway.
How do i do this the "right" way?
Do i need to run some cleanup scripts or do..

1. Alltasks at publisher - Delete subscription
2. Alltasks at publisher - Delete publication
3. Drop database at subscription server
4. Create new publication and snapshot
5. Create new Subscription

Is this enough? or am i missing something?
Database is large ~200Gb so it will take some time.
arunyadav007
arunyadav007
SSC Rookie
SSC Rookie (42 reputation)SSC Rookie (42 reputation)SSC Rookie (42 reputation)SSC Rookie (42 reputation)SSC Rookie (42 reputation)SSC Rookie (42 reputation)SSC Rookie (42 reputation)SSC Rookie (42 reputation)

Group: General Forum Members
Points: 42 Visits: 299
Hi,

Please refer to the below:

http://social.msdn.microsoft.com/Forums/is/sqlreplication/thread/62adf53b-6506-4df4-b914-2ff299c0adf5
Knut_knut
Knut_knut
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 355
Thx, this should be the right way since i only have one subscriber i dont have anything to worry about.
And even if i have more subscribers as long as i don't, in thoose cases do this on the Publisher

However in this case i will do it on Subscriber and after that i will do it on Publisher
(I only have one subscriber)

exec sp_removedbreplication 'databasename'
exec sp_replicationdboption 'databasename','merge publish','false'

When this is done i will recreate the replication

it's allways a bit nervous when it comes to production enviroments...
Don't wanna mess upp a big prod database...and i dont wan't errors due to delete the wrong way.
I guess they have done it wrong before thats why i have this problem now...

Sry for any bad english....
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search