February 10, 2010 at 6:59 pm
Hi
I had replication set up for one table and the replication was going fine. I dropped the subscriber=> dropped the publisher => added one more table at both Publisher & the subscriber. When i try to create a new publisher, i chose the option "Keep existing table and data" instead of drop and recreate since i did not want the subscriber data to be touched. Now i am seeing the synchronization status generating / copying full dump of data in the shared unc folder.
- Is this normal behaviour? What if the tables size is 100s of GB? How do i tell SQL Server replication to worry only about data to be inserted?
February 15, 2010 at 1:19 pm
Found the solution. The trick is to use sp_add_article , sp_addsubscription with the latest LSN. It should not result in duplicates being geneated (-SkipError "2627" can then be used).
I am posting this since it might be of help to those facing similar situation.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply