Timeline for How to properly clean Merge Replication Setup
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 24, 2013 at 15:41 | comment | added | Brandon Williams | I have posted my answer already with the correct way to remove a Merge publication and subscription(s). Your approach is suggesting users delete from system tables which is unsupported and wrong. | |
| Jun 24, 2013 at 15:39 | comment | added | Kin Shah | @BrandonWilliams The question is not how to drop merge replicaiton, it is how to clean up Merge replication after it is not dropped correctly. | |
| Jun 24, 2013 at 15:26 | comment | added | Brandon Williams | This is not how you drop a Merge topology. | |
| Jun 20, 2013 at 2:27 | vote | accept | Adel Khayata | ||
| Jun 20, 2013 at 2:26 | vote | accept | Adel Khayata | ||
| Jun 20, 2013 at 2:26 | |||||
| Jun 19, 2013 at 14:07 | comment | added | Kin Shah | @AdelKhayata you have to put in the publication Name. | |
| Jun 19, 2013 at 6:22 | comment | added | Adel Khayata | Also you are using a filter in the query ( and p.name = '') which is trying to select a publication which has no name. | |
| Jun 19, 2013 at 6:22 | comment | added | Adel Khayata | I was trying your script in step 3, but it seems that trigger names in my case starts with MSmerge_ instead of ('ins' or 'upd' or 'del' ) like you presume, which is causing the list of drop trigger script to be empty, Is it expected to be different between systems ? | |
| Jun 18, 2013 at 19:46 | history | edited | Kin Shah | CC BY-SA 3.0 | deleted 46 characters in body |
| Jun 18, 2013 at 17:24 | history | answered | Kin Shah | CC BY-SA 3.0 |