Drop merge repliaction the right way

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 High Availability » Drop merge repliaction the right way

Drop merge repliaction the right way

Rate Topic

Display Mode

Topic Options

Author

Message

Knut_knut

Posted Tuesday, December 04, 2012 5:56 AM

Grasshopper

Group: General Forum Members
Last Login: Friday, April 12, 2013 5:11 AM
Points: 16, Visits: 241

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.

Post #1392402

arunyadav007

Posted Tuesday, December 04, 2012 6:28 AM

SSC Rookie

Group: General Forum Members
Last Login: Friday, May 03, 2013 3:06 AM
Points: 42, Visits: 285

Hi,

Please refer to the below:

http://social.msdn.microsoft.com/Forums/is/sqlreplication/thread/62adf53b-6506-4df4-b914-2ff299c0adf5

Post #1392421

Knut_knut

Posted Tuesday, December 04, 2012 6:45 AM

Grasshopper

Group: General Forum Members
Last Login: Friday, April 12, 2013 5:11 AM
Points: 16, Visits: 241

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....

Post #1392443

« Prev Topic | Next Topic »

Permissions